May 6, 2013 at 1:29 pm
I set up log shipping on both servers and they are running fine. Due to a recent requirement, they want a database snapshot on secondary server/database to run report.
I create snapshot database, but log shipping starts failing until I drop the snapshot database. Is there a way to go around it? I don't want database mirroring in this case.
Thanks,
Minh
May 6, 2013 at 2:22 pm
What kind of error you are getting? If you post the error message might be able to help you.
May 6, 2013 at 3:03 pm
There was no specific error. The restore job in logshipping just failed with no msg. Right after I drop the snapshot, the restore job runs fine without any problem. I tested this couple time and it always happened like that. I'd like to know if the combination of logshipping + db snapshot will work or not. According to MS, db snapshot only works with db mirroring.
Thanks,
Minh
May 6, 2013 at 3:18 pm
So could you be more specific? 2 servers- DO they have same databases/ different databases?
Which DB you are using to to create snapshot & where?
Have to tried replication instead of snapshot? It will solve your reporting issue.
May 6, 2013 at 3:34 pm
Yes, I have 2 servers (both s2k8 enterprise)
I used secondary database on the warm standby to create snapshot, not the source on primary server, and I want my users to run the report on this standby server.
Yes, I know I can use replication, database mirroring for my environment, but I'm more interested to know if there is anyone out there using logshipping/db snapshot successfully.
My log shipping runs every 15min, and I want my snapshot get refreshed every 5hr.
Minh
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply