Databases
StackOverflow2013
Postsdbo
POBest practice for a SQL Archiving Stored Procedure
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practice for a SQL Archiving Stored Procedure
    primarykey
    data
    text
    <p>I have a very large database (~100Gb) primarily consisting of two tables I want to reduce in size (both of which have approx. 50 million records). I have an archive DB set up on the same server with these two tables, using the same schema. I'm trying to determine the best conceptual way of going about removing the rows from the live db and inserting them in the archive DB. In pseudocode this is what I'm doing now:</p> <pre><code>Declare @NextIDs Table(UniqueID) Declare @twoYearsAgo = two years from today's date Insert into @NextIDs SELECT top 100 from myLargeTable Where myLargeTable.actionDate &lt; twoYearsAgo Insert into myArchiveTable &lt;fields&gt; SELECT &lt;fields&gt; FROM myLargeTable INNER JOIN @NextIDs on myLargeTable.UniqueID = @NextIDs.UniqueID DELETE MyLargeTable FROM MyLargeTable INNER JOIN @NextIDs on myLargeTable.UniqueID = @NextIDs.UniqueID </code></pre> <p>Right now this takes a horrifically slow 7 minutes to complete 1000 records. I've tested the Delete and the Insert, both taking approx. 3.5 minutes to complete, so its not necessarily one is drastically more inefficient than the other. Can anyone point out some optimization ideas in this? </p> <p>Thanks!</p> <p>This is SQL Server 2000.</p> <p>Edit: On the large table there is a clustered index on the ActionDate field. There are two other indexes, but neither are referenced in any of the queries. The Archive table has no indexes. On my test server, this is the only query hitting the SQL Server, so it should have plenty of processing power. </p> <p>Code (this does a loop in batches of 1000 records at a time):</p> <pre><code> DECLARE @NextIDs TABLE(UniqueID int primary key) DECLARE @TwoYearsAgo datetime SELECT @TwoYearsAgo = DATEADD(d, (-2 * 365), GetDate()) WHILE EXISTS(SELECT TOP 1 UserName FROM [ISAdminDB].[dbo].[UserUnitAudit] WHERE [ActionDateTime] &lt; @TwoYearsAgo) BEGIN BEGIN TRAN --get all records to be archived INSERT INTO @NextIDs(UniqueID) SELECT TOP 1000 UniqueID FROM [ISAdminDB].[dbo].[UserUnitAudit] WHERE [UserUnitAudit].[ActionDateTime] &lt; @TwoYearsAgo --insert into archive table INSERT INTO [ISArchive].[dbo].[userunitaudit] (&lt;Fields&gt;) SELECT &lt;Fields&gt; FROM [ISAdminDB].[dbo].[UserUnitAudit] AS a INNER JOIN @NextIDs AS b ON a.UniqueID = b.UniqueID --remove from Admin DB DELETE [ISAdminDB].[dbo].[UserUnitAudit] FROM [ISAdminDB].[dbo].[UserUnitAudit] AS a INNER JOIN @NextIDs AS b ON a.UniqueID = b.UniqueID DELETE FROM @NextIDs COMMIT END </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKevin
    1. USKevin
    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
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest practice for a SQL Archiving Stored Procedure
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest practice for a SQL Archiving Stored Procedure
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBest practice for a SQL Archiving Stored Procedure
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you have a clustered index on the primary key field?
      singulars
      1. POBest practice for a SQL Archiving Stored Procedure
      1. USfeihtthief
    2. COIs NextIDs a table variable or a temp table? If it is a table variable, try a temp table instead. I have had performance problems with table variables in SQL Server 2000; although not this bad.
      singulars
      1. POBest practice for a SQL Archiving Stored Procedure
      1. USDarryl Peterson
    3. CONextID's is currently declared as a Table Variable. I'll experiment with using a temp table.
      singulars
      1. POBest practice for a SQL Archiving Stored Procedure
      1. USKevin
 

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