| By product |
| Other |
|
Troubleshooting Troubleshooting and known issues with ApexSQL Tools Very large ApexSQL Log tables Applies to ApexSQL Log Summary This article explains why the APEXSQL_LOG_CONNECTION_MONITOR_SESSION and APEXSQL_LOG_LOGIN tables can grow enormously and how to make them smaller Symptoms The database where the tables that capture login, application and host information are stored (APEXSQLLOG by default) has grown enormously (I.e. 15 GB). The APEXSQL_LOG_LOGIN and APEXSQL_LOG_CONNECTION_MONITOR_SESSION tables have millions of records Cause ApexSQL Log Connection monitor inserts one new row into APEXSQL_LOG_LOGIN table for each new login and one new row into APEXSQL_LOG_CONNECTION_MONITOR_SESSION table for each new session. These tables grow with the number of logins made to the server. The location of these tables and data management is fully configurable from the Connection monitor manager dialog. More information could be found here Resolution The login information is not cleaned automatically if the option I will maintain the information myself is selected. The recommended solution is to use automatic maintenance of captured information. If there is no need to keep the captured data of the changes that happened long ago, reduce the number of days that the information is kept for  Also, if there is no need for the specific connecton information captured by Connection monitor, this could be stoped and disabled. Note that deleting the captured data will make the database transaction log grow. But it will also enable to recover the deleted data using ApexSQL Log About ApexSQL Log ApexSQL Log is a SQL Server Transaction Log reader that allows viewing transaction log data in read-friendly format. Audit and undo SQL database changes of your choosing. Determine who changed the data and when the change occurred. Read the transaction log to find out who created, changed or dropped a database object Last updated November 29, 2011 Labels: ApexSQL Log 4 Comments:At January 15, 2009 1:07 PM, swl said...
I operate a consumer website and I just found that 138GB was in this bl**dy table. It was hidden away in the system database. I would advise making new customers more aware of this process. At March 31, 2009 5:37 PM, guptam said...
Agree I didn't know Apex Log did this; until I noticed my disk free space went down magically.  said...
Same here, i really wanst aware that Apex did something in msdb database, when i see 25 gig msdb and all is in APEXSQL_LOG_LOGIN table. I really dont remember i install something in msdb database or i have been asked to install there !! Dmitriy Dyubchenko said...
You need just execute the following commands to stop Connection Monitor: << Home |
