Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Log Shipping Problem

Author  Topic 

SqlZ
Yak Posting Veteran

69 Posts

Posted - 2003-07-15 : 10:08:59
Not really a problem but didn't know what else to call this. Here is my situation: I have one particular table in a database that gets truncated and repopulated every night (~2.5 million recs). All my databases get their logs shipped to our Disaster Recovery site every 15 minutes. While this works well for the majority of my databases, the APS database just dies because of the one fifteen minutes where it sees 2 million transactions. Any suggestions? I know this is pretty vague and I apologize, but I think this is an architecture problem and I need to find a better way to restore this db to my DR site.

Thanks in advance

"DBAs are overpaid and their jobs are easy...heck, I could do it."

-Quote from a former boss who calls often for help and speaks to my voice mail :)

setbasedisthetruepath
Used SQL Salesman

992 Posts

Posted - 2003-07-15 : 10:14:09
Don't log the repopulation and you'll be fine. If you really are issuing a TRUNCATE TABLE, that's not logged by default, so changing the recovery model of the db to 'simple' just before the truncate/insert and changing it back after should do it.

Jonathan
{0}
Go to Top of Page

SqlZ
Yak Posting Veteran

69 Posts

Posted - 2003-07-15 : 10:26:56
I thought about that but won't that break log shipping because it requires the "Full" recovery model.

Also, how would the new data be shipped to my DR site if it has no log of the new data in the source DB?

Sorry for the questions but I am new to log shipping.
Go to Top of Page

setbasedisthetruepath
Used SQL Salesman

992 Posts

Posted - 2003-07-15 : 10:31:49
If all you're doing is truncate/reload, don't log ship at all. Just push the data over through a DTS package, if at all. With that data pattern the actual data is usually "worthless" as it can be recreated, thus no need to backup. That should have been my first recommendation .

Edited by - setbasedisthetruepath on 07/15/2003 10:32:53
Go to Top of Page

SqlZ
Yak Posting Veteran

69 Posts

Posted - 2003-07-15 : 10:55:13
I also think DTS is the way to go. The only reason why I am backing up at all is because there are other tables in the APS DB with valuable data. Otherwise I fully agree with not backing up at all. Thanks SBTP.
Go to Top of Page
   

- Advertisement -