Databases
StackOverflow2013
Postsdbo
PODeleting large amount of data from SQL Server database
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODeleting large amount of data from SQL Server database
    primarykey
    data
    text
    <p>I am trying to purge large amounts of historical data from our database for any data older than 13 months. </p> <p>I have written a stored procedure for truncation, however when I try to run them I have two problems.</p> <p>Problem 1 - the deletion fills up the database transaction logs and crashes the database when the disk drives run out of space.</p> <p>Problem 2 - The script itself takes a long time to execute. </p> <p>Below are the statements in the SP:</p> <pre><code>DELETE FROM Header_Table WHERE Date_DT &lt; @date </code></pre> <p>The <code>Header_Table</code> table has a <code>ON DELETE CASCADE</code> relationship with 10 other tables. That means when I fire the above query it deletes the data from the <code>Header_Table</code> table as well as from the 10 tables reference by <code>Header_Table</code></p> <ol> <li><p>And in the second statement, I am inserting the data from the <code>Information_Table</code> table to temp table.</p> <pre><code>INSERT INTO Temp_Table (Key, AccNum, Exp, Name_VC) SELECT in.Key AS CRD_NFO_CIK, in.Acct_Num AS CRD_NFO_ACC, in.Exp AS CRD_NFO_EXP, in.Name_on_Card_VC AS CRD_NFO_NAME FROM Information_Table in LEFT OUTER JOIN Card_T crd ON in.Key = crd.Card_Info_Key LEFT OUTER JOIN Business_T business ON in.Key = business.CC_Info_Key LEFT OUTER JOIN Con_T contr ON in.Key = contr.Card_Info_Key LEFT OUTER JOIN Customer_Payment_T customer ON in.Key = customer.Card_Info_Key LEFT OUTER JOIN Temp_Table Temp ON in.Key = Temp.Key WHERE Temp.Key IS NULL AND crd.Card_Info_Key IS NULL AND business.CC_Info_Key IS NULL AND contr.Card_Info_Key IS NULL AND customer.Card_Info_Key IS NULL </code></pre></li> <li><p>In the below statement, I am actually deleting the data from the Information_Table</p> <pre><code> DELETE info FROM Information_Table in LEFT OUTER JOIN Card_T crd ON in.Key = crd.Card_Info_Key LEFT OUTER JOIN Business_T business ON in.Key = business.CC_Info_Key LEFT OUTER JOIN Con_T contr ON in.Key = contr.Card_Info_Key LEFT OUTER JOIN Customer_Payment_T customer ON in.Key = customer.Card_Info_Key WHERE crd.Card_Info_Key IS NULL AND business.CC_Info_Key IS NULL AND contr.Card_Info_Key IS NULL AND customer.Card_Info_Key IS NULL </code></pre></li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDnyan Waychal
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODeleting large amount of data from SQL Server database
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. CO"The Header_Table table has a ON DELETE CASCADE relationship with 10 other tables." - This will *definitely* take a lot of time for any delete operation on that table. You may get more performance if you "manually" delete the (batches of) records from each of the tables one after another.
      singulars
      1. PODeleting large amount of data from SQL Server database
      1. USJimmyB
    2. CO@HannoBinder Actully we are not aware of the further CASCADE'ing relationship for 10 tables. As this is clients production database, we cannot take much risk to delete table records manually.
      singulars
      1. PODeleting large amount of data from SQL Server database
      1. USDnyan Waychal
    3. COHmm, too bad. Considering the transaction log [this](http://databases.about.com/od/sqlserver/a/truncate_shrink.htm) may be helpful. - Deleting records in *batches* will be the way to go anyway, which also gives you control over how long the operation runs without interruption; you may want to make batches of, say, 4 weeks worth of data and delete one of these batches each night until you catch up with the table's growth. Don't forget to `commit` (at least) after each batch to release any locks and allow the transaction log to be shrunk.
      singulars
      1. PODeleting large amount of data from SQL Server database
      1. USJimmyB
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload