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

Trouble with log shipping. Reporting Server. Expand / Collapse
Author
Message
Posted Thursday, January 24, 2013 7:03 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:31 AM
Points: 706, Visits: 1,752
Hi,

This is a new setup I'm trying to accomodate load.

I have server A that is production server. I have server B which is the exact same DB on server A that will be used only for reporting.

I have log shipping setup between server A and server B. Log shipping works ( I have DB B setup as standby/read only) - it works but if I run a query, then check my log shipping job I get the log shipping job error:

"Exclusive access could not be obtained because database is in use"

I need server B to be my report server, so I can't have it not complete the log shipping.

What can I do? I need server A and server B to be in sync and be 'reportable'..



Post #1411119
Posted Thursday, January 24, 2013 7:08 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Monday, December 8, 2014 1:45 AM
Points: 5,221, Visits: 5,120
You will need to ensure that you have selected disconnect users when restoring.

You cannot restore a log if the DB is being used by a user.

So if your logshipping is set to restore every 15 minutes, users will be kicked out every 15 minutes while it restores the log.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1411121
Posted Thursday, January 24, 2013 7:52 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:31 AM
Points: 706, Visits: 1,752
Guessing it kick out my users if they are in the middle of running a report?

If so, that would be bad.

Do I have any other options for my senario?



Post #1411147
Posted Friday, January 25, 2013 1:53 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Monday, December 8, 2014 1:45 AM
Points: 5,221, Visits: 5,120
Transactional Replication would be the only real alternative.

Unless you can live with delays when you can write your own SSIS packages to transfer new data, updated data, deleted data at a regular interval.

But that would depend on your database being up to the task with auditing on when things get deleted updated inserted. If you can upgrade to 2008 Enterprise you could look at change data capture.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1411526
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse