Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
Diagnostic tracing data is gathered during a tracing session. A tracing session can be captured in one of three ways:
When a tracing session is in progress, SQL Anywhere generates diagnostic information for that database. The amount of tracing data generated depends on the tracing settings. For more information about how to configure the amount and type of tracing data generated, see Configuring diagnostic tracing.
The database being profiled is either referred to as the production database, the source database, or simply the database being profiled. The database into which the tracing data is stored is referred to as the tracing database. The production and tracing database can be the same database. However, storing tracing data in a separate database is recommended since doing so avoids growing the size of the production database. This is important since database files cannot be reduced to a smaller size once they have grown. Also, the production database performs better if the overhead for storing and maintaining tracing data is performed in another database, especially if the production database is large and experiences heavy usage.
The tables in the tracing database that hold the tracing data are referred to as the diagnostic tracing tables. These tables are owned by dbo. For more information about these tables, see Diagnostic tracing tables.
The Application Profiling Wizard is not supported on Windows Mobile; however, the Database Tracing Wizard is. As well, you must trace from the Windows Mobile device to a copy of the Windows Mobile database running on a database server on a desktop computer. You cannot automatically create a tracing database from a Windows Mobile device, and you cannot trace to the local database on a Windows Mobile device.
The files created and used for a tracing session differ depending on whether you use the Application Profiling Wizard, or the Database Tracing Wizard.
When you run the Application Profiling Wizard, the wizard silently captures a tracing session behind the scenes, creating the tracing database to hold the diagnostic tables. This external database is created using the name and location you specify in the wizard, and it has the extension .adb. The wizard also creates an analysis log file in the same directory as the tracing database, using the same name but with the extension .alg. This analysis log file contains the results of the analysis work done by the wizard, and can be opened at any time in a text editor.
Once you are done with the recommendations provided by the Application Profiling Wizard, you can delete the tracing database and analysis log file associated with the session.
When you create a tracing session using the Database Tracing Wizard, the wizard asks you choose whether to save tracing data internally, in the production database, or externally, in a separate database (for example, tracingData.db). Creating an external tracing database is recommended. See Creating an external tracing database.
Tracing information is not unloaded as part of a database unload or reload operation. If you want to transfer tracing information from one database to another, you must do so manually by copying the contents of the sa_diagnostic_* tables; however, this is not recommended.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|