Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Archiving data to improve backup performance Expand / Collapse
Author
Message
Posted Monday, October 11, 2010 8:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 27, 2012 9:36 AM
Points: 3, Visits: 17
There are three databases located on three separate servers around the country (Miami, Los Angeles and New York). These three databases are roughly 20-30 Gb. The current practice is to use transaction log shipping (actually a modified process that compresses/decompresses the logs for shipping and application) to update backup (data repository) copies of each of the three databases on a central SQL server in a different New York location.

The three production databases are backed up nightly, as are the data repositories. The growth of the amount of data has created performance issues with the production databases.

What I would like to do is a) turn off log shipping, b) delete the excess data from the production tables, and c) turn log shipping back on.

The questions I have are:

Can I apply transaction logs to the database if the number of records in the tables are different?

The data to be deleted (all records over six months old) will not be changing, so will the transaction logging application process fall over?

Will I be able to turn off logging in order to delete the old data, or will the data be deleted from the repository once I delete it from the production database and then turn log shipping back on?

Am I doing this entirely the wrong way? Note that I did not set up this database backup scheme (log shipping) and am not free to make any change that I wish.
Post #1002207
Posted Monday, October 11, 2010 9:08 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, November 15, 2011 6:31 AM
Points: 2,798, Visits: 7,061
are you saying that the amount of data is causing the full backup to take too long ? or is the problem that the databse is performing badly?

becasue at 20 - 30Gb i can't really see the backups taking that long as the database are not very large
Post #1002242
Posted Monday, October 11, 2010 9:13 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 10:34 AM
Points: 1,235, Visits: 2,210
Turning off & on logshipping will require reinitialization. (full backup + new logfiles).
Mayhaps is it possible to delete the old data in sustainable batches for logshipping?
Post #1002249
Posted Monday, October 11, 2010 11:06 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, March 27, 2012 9:36 AM
Points: 3, Visits: 17
Yes, the backups are affecting performance on the servers - this is a 24/7 operation, so there isn't really any downtime.
Post #1002346
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse