text: Speech application event logging data is stored in event trace log (.etl) log files. To view and analyze the data in .etl files, first import it to these databases:
  Separate databases are required for each of the two tools. To view reports you need to import the .etl files into a database for use by Speech Application Reports. To analyze calls at event-level detail in Call Viewer, a separate database with a different schema is required. The recommended tool for importing log files into these databases is Microsoft SQL Server 2000 Data Transformation Services (DTS). As an alternative, use the MSSLogToDatabase command line tool.
  The following steps are recommended in order to minimize the impact of creating large .etl files.
  In order to minimize the time needed to import data and to reduce the risk of impairing MSS performance, the following steps are recommended.
  To include additional event types for use in your own custom reports, list events in a .txt file and specify the file when creating the database. Include each event type on a separate line. List each event type desired for the custom report.
  The event types are classes in the Microsoft.SpeechServer.Log namespace. When listing event types the namespace should be omitted. Only the event type name is required. The event classes are structured hierarchically and implement an inheritance model. As a result, if a parent type is listed the children are also added to the database. For information on the event schema, begin with the topic Event Logging Class Hierarchy.
  To get complete information in the Call Summary tab in Call Viewer, include at least the following event types when importing from .etl files to the Call Viewer database:
  If these event types are not included in the import, the Calls table in the Call Viewer database is populated largely with null values. As a result, queries in Call Viewer display mostly null values.
  The maximum file size on a FAT32 volume is 4 GB. Since speech application .etl files can be very large, it is possible to exceed the 4 GB limit when importing log files into a database. The workaround is to create multiple data files in the primary filegroup as described in the topic Physical Database Files and Filegroups in the MSDN Library.
  Microsoft Speech Application Log Analysis Tools 1.1