Diagnostic tracing data is gathered during a tracing session. Three methods are available to capture tracing session data:
When a tracing session is in progress, SQL Anywhere generates diagnostic information for the specified 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 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, to avoid increasing the size of the production database, it is recommended that you store tracing data in a separate database. The size of database files cannot be reduced after 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 heavily used.
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.
Discuss this page in DocCommentXchange.
|Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0|