When trying to run a DELETE on a large set of data (23,416,618 records as of today) we observed twice this behaviour:
query runs for over 6 hours at which point transaction log goes over 60G in size and we stop it
DB goes into recovery mode and restores all records. It appears to be a SQL server performance problem.
Below are the sizes of referenced tables and the actual SQL statement.
Please advise how we could rectify this? Many thanks.
|
SQL Server version: MS SQL Server 2008 R2 Enterprise SP1.
CPU: 2
RAM: 24G
HD:
C drive, 250G, holds database and transaction log.
D drive, 300G, holds database and transaction log backup.
Current (Atlassian) "bamboo" database size is 51G, transaction log is 52Mb.