Problem using Log Shipping in Standby method | SQL Server Performance Forums
SQL Server Performance Forum – Threads Archive
Problem using Log Shipping in Standby methodHello all,
Please let me know how can I use read-only database, which is participated in Log Shipping to off load reports. It’s not possible to map users in database to related logins in SQL.
Any idea will be greatly appreciated.
Unless the database is in standby the users will not be able to access the database, also during the log restores all the users must be disconnected from the standby database.From other forum: To load the t-logs, SQL Server needs exclusive access to the DB. So:
a) you allow read only access to continue, which can potentially block the t-log load
b) allow the t-log load, knowing that users will not be able to access the DB while the t-log is loading
c) kill the connections to the DB when the t-log is about to load, effectively creating b), but making unhappy end users
d) use another reporting solution
Log shipping has always been meant for creating a standby. While you can use it for read only access, it is not the best use of log shipping, and never has been. I have never ever recommended this configuration. YOu are better off setting up another way to do reporting and leave log shipping alone.
http://blogs.msdn.com/rdoherty/archive/2006/06/30/652011.aspx – SQL 2005
Thank you so much for the reply.
As a matter of fact, I made a big mistake regarding user creation in the secondary server. I had created the same users in secondary server without pay attention to SID. Now I have transfer login with SP_HELP_REVLOGIN, configured log shipping and every th9ing works fine.