Home Forums SQL Server 2012 SQL 2012 - General Design considerations for database cleanup application. RE: Design considerations for database cleanup application.

  • June 25, 2013 at 12:59 pm

    #1627268

    mayurkb (6/25/2013)

    Thanks for the reply Sean.

    1. The other applications won't be using that data, since it is old data. So it does not impact them.

    2. There won't be millions of records. There will be thousands or less.

    So just create the delete statements, put it all into a stored proc and fire it off once a day. You may see some slight delays in the other processes but for a few thousand rows the wait time on deletes will probably not even be noticed.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/