Archive Log Data
You can use Microsoft SQL Server™ Data Transformation Services (DTS), SQL Server Agent, or some other similar application to archive event and performance counter log data before it is cleaned-up or summarized from the log.
To archive event data by using DTS to copy tables
You must use SQL Server to access the Application Center Events and Performance Logging database. You can export the information to various formats, including SQL Server tables, Microsoft Excel spreadsheets, and Microsoft Access databases. For a Microsoft Access database, you must create a *.mdb file on the target before it can be written to.
Application Center uses a named instance of the SQL Server Desktop Engine. When you specify the database, you must specify the named instance server_name $MSAC.
In the SQL Server Enterprise Management snap-in, add a new SQL Server registration for each cluster member.
Note You can also add the SQL Server Enterprise Management snap-in to the Application Center snap-in.
Right-click a newly-registered server node, on the pop-up menu, click All Tasks, and then click Export Data.
In the Data Transformation Import/Export Wizard, click Next.
In the Database box, click ACLog, and then click Next.
In the Server box, enter the target name.
Use Copy table(s) to copy over the various tables as-is (this option is selected by default).
Select the various tables to copy over, and then click Next.
You can run the operation immediately and only once, or select the Schedule DTS check box, and then click the ellipsis button to configure a scheduled export.
The tables are copied to the target.
For more information about generating reports, see Generating Reports and Archiving Data.
For more information about the SQL Server Agent, DTS, adding a SQL Server registration, exporting methods, and the Data Transformation Import/Export Wizard, see the SQL Server Help.
For more information about adding a snap-in to a snap-in, see the Windows 2000 Help.
Did you find this information useful? Please send your suggestions and comments about the documentation to firstname.lastname@example.org.