SQL Monitor - 2.3
tempdb size increases when clearing purge backlog - SQL Monitor
In SQL Monitor 2.2, improvements have been made to the way data is purged from the Data Repository database. Purging is now performed as a faster, background task that reduces the affect on general performance of clearing a backlog of purged data. To facilitate this, SQL Monitor has increased its usage of tempdb, so you may see tempdb grow by up to half the size of your Data Repository database when SQL Monitor is clearing a large backlog.
Once the backlog of data has been purged successfully, restart the SQL Server service and tempdb's size will revert back to normal.
A significant backlog of data that needs purging may build up if you perform any of the following actions:
- change your current purging policy to keep data in the Data Repository for a shorter amount of time
- update a large SQL Monitor database to version 2.2
- remove a monitored server and delete all existing data for the server from the Data Repository
While the Data Repository database is busy with these actions, you may notice reduced performance while using the SQL Monitor interface.
Was this article helpful?
Using SQL MonitorSQL Monitor
- Example configuration of SQL Monitor using virtualization software
- Retrieving alert settings using SQL Data Compare
- Licensing issues with SQL Monitor
- Log files in SQL Monitor
- Upgrading to a later version of SQL Monitor
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Monitor
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs
