seagate Crystal Reports groups several commonly used commands on the Standard Toolbar, which remains on screen at all times (unless you decide to toggle it off with the Toolbars command).
The Standard toolbar eliminates some of the steps needed to activate the commands and can thus greatly speed your work in creating reports. Each command available via the Standard toolbar is discussed in online Help (search for each command by name).
In the 32-bit version of Seagate Crystal Reports, you can move the Standard Toolbar to another fixed location within the window or set it up as a floating palette. See How to move and resize toolbars and Formatting Toolbar.
If you are not sure about the function of a button on the Standard Toolbar, place the pointer over the button and hold it there. A Tool Tip appears, providing a description of the button.
The buttons on the Standard toolbar perform the following functions:
Creates a new report.
Opens an existing report.
Saves the report.
Sends the report to a printer.
Previews the report in the Preview Tab.
Exports the report to a file or e-mail.
Refreshes report data.
Cuts selected object/data to the Clipboard.
Copies the selected object/data to the Clipboard.
Pastes object/data from Clipboard to the report.
Undoes an action.
Redoes an action.
Inserts database, formula, parameter, and group name fields.
Insert a text object.
Inserts a summary.
Activates the Report Expert.
Formats any section of the report.
Sets record/group selection criteria.
Sets record sort order.
Inserts a chart.
Inserts a Map.
Searches for a specific record.
Sets the magnification factor for viewing your report.
Context-sensitive Help.
search software
How to Monitoring with SQL Profiler
SQL Profiler is a graphical tool that allows system administrators to monitor events in an instance of Microsoft® SQL Server™. You can capture and save data about each event to a file or SQL Server table to analyze later. For example, you can monitor a production environment to see which stored procedures are hampering performance by executing too slowly.
Use SQL Profiler to monitor only the events in which you are interested. If traces are becoming too large, you can filter them based on the information you want, so that only a subset of the event data is collected. Monitoring too many events adds overhead to the server and the monitoring process and can cause the trace file or trace table to grow very large, especially when the monitoring process takes place over a long period of time.
After you have traced events, SQL Profiler allows captured event data to be replayed against an instance of SQL Server, thereby effectively reexecuting the saved events as they occurred originally.
Use SQL Profiler to:
Monitor the performance of an instance of SQL Server.
Debug Transact-SQL statements and stored procedures.
Identify slow-executing queries.
Test SQL statements and stored procedures in the development phase of a project by single-stepping through statements to confirm that the code works as expected.
Troubleshoot problems in SQL Server by capturing events on a production system and replaying them on a test system. This is useful for testing or debugging purposes and allows users to continue using the production system without interference.
Audit and review activity that occurred on an instance of SQL Server. This allows a security administrator to review any of the auditing events, including the success and failure of a login attempt and the success and failure of permissions in accessing statements and objects.
SQL Profiler provides a graphical user interface to a set of stored procedures that can be used to monitor an instance of SQL Server. For example, it is possible to create your own application that uses SQL Profiler stored procedures to monitor SQL Server.
You must have at least 10 megabytes (MB) of free space to run SQL Profiler. If free space drops below 10 MB while you are using SQL Profiler, all SQL Profiler functions will stop
Use SQL Profiler to monitor only the events in which you are interested. If traces are becoming too large, you can filter them based on the information you want, so that only a subset of the event data is collected. Monitoring too many events adds overhead to the server and the monitoring process and can cause the trace file or trace table to grow very large, especially when the monitoring process takes place over a long period of time.
After you have traced events, SQL Profiler allows captured event data to be replayed against an instance of SQL Server, thereby effectively reexecuting the saved events as they occurred originally.
Use SQL Profiler to:
Monitor the performance of an instance of SQL Server.
Debug Transact-SQL statements and stored procedures.
Identify slow-executing queries.
Test SQL statements and stored procedures in the development phase of a project by single-stepping through statements to confirm that the code works as expected.
Troubleshoot problems in SQL Server by capturing events on a production system and replaying them on a test system. This is useful for testing or debugging purposes and allows users to continue using the production system without interference.
Audit and review activity that occurred on an instance of SQL Server. This allows a security administrator to review any of the auditing events, including the success and failure of a login attempt and the success and failure of permissions in accessing statements and objects.
SQL Profiler provides a graphical user interface to a set of stored procedures that can be used to monitor an instance of SQL Server. For example, it is possible to create your own application that uses SQL Profiler stored procedures to monitor SQL Server.
You must have at least 10 megabytes (MB) of free space to run SQL Profiler. If free space drops below 10 MB while you are using SQL Profiler, all SQL Profiler functions will stop
Subscribe to:
Posts (Atom)
