December 26, 2010 at 11:52 pm
Hi,
Is it possible to create report on the secondary server configured for log shipping? Please let me know.
Thanks
December 27, 2010 at 8:52 am
If the secondary database is in "Standby" mode, it is available for Read-only access.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
December 27, 2010 at 1:53 pm
gttred (12/26/2010)
Hi,Is it possible to create report on the secondary server configured for log shipping? Please let me know.
Thanks
Have a look on this
http://msdn.microsoft.com/en-us/library/ms189572.aspx
Thanks
Parthi
Thanks
Parthi
December 27, 2010 at 2:07 pm
Be aware that when logs are restored, all connections to the database need to be broken, so you might want to adjust your restore schedule to prevent issues with people trying to run reports.
December 28, 2010 at 10:10 am
Steve Jones - SSC Editor (12/27/2010)
Be aware that when logs are restored, all connections to the database need to be broken, so you might want to adjust your restore schedule to prevent issues with people trying to run reports.
BAH! Just KILL their connections! 😀 I do that for several clients who are using a log ship box for a reporting instance - one of them with many thousands of databases on a single server!
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
December 28, 2010 at 11:46 am
TheSQLGuru (12/28/2010)
BAH! Just KILL their connections! 😀 I do that for several clients who are using a log ship box for a reporting instance - one of them with many thousands of databases on a single server!
Jones is correct while we restore we need to kill the existing connections then only we can restore the remaining Txns logs.
You can reduce the load on your primary server by using a secondary server for read-only query processing. To do this, the secondary database must be in STANDBY mode. You will not be able to run queries if the database is in NORECOVERY mode. For more information about database modes.
There are two options for configuration when you place the secondary database in standby mode:
You can choose to have database users disconnected when transaction log backups are being restored. If you choose this option, users will be disconnected from the database each time the log shipping restore job attempts to restore a transaction log to the secondary database. Disconnection will happen on the schedule you set for the restore job.
You can choose not to disconnect users. In this case, the restore job cannot restore transaction log backups to the secondary database if there are users connected to that database. Transaction log backups will accumulate until there are no user connections to the database.
Thanks
Parthi
Thanks
Parthi
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply