Archive and purge live transaction table

Question

0.00/5 (No votes)

See more:

SQL-Server-2008R2

The is Log table in production which receive entries from various applications. The Log table receives around 5000 rows per second. As per client requirement, they want to run a hourly job to copy all records to Archive Log table and delete all the copied records from Log table. This will happen while 5000 rows per second inserts are committing.

My approach:

SQL

DECLARE @startID AS integer
DECLARE @endID AS integer

SET @startID = (SELECT MIN(ID) FROM Log)
SET @endID   = (SELECT MAX(ID) FROM Log)
INSERT INTO ArchiveLog SELECT * FROM Log WHERE ID BETWEEN @startID AND @endID
Delete FROM LOG WHERE ID BETWEEN @startID AND @endID

What would be the best possible approach to do this in an fast and optimized way? Please suggest.

Thanks in advance.

Posted 16-Jan-15 19:56pm

Wild-Programmer

Updated 16-Jan-15 20:19pm

Wendelius

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Accepted Answer · 2015-01-16T20:28:00

Based on the information you provided your approach seems valid to me. Few things I would do

Ensure that the ID is unique and indexed
Typically I discourage the use of NOLOCK hint but in this case I believe it may be justified. See for example What should be considered when NOLOCK hint is used[^]
If the deletion takes too much time and the transaction starts to block others run the deletion in a loop and delete smaller portions of records. With each iteration commit the deletion. Depending on the logic you may have to add check that the row exists in the archivelog table