October 5, 2010 at 10:59 am
We're looking to implement log shipping on our production server. However, there are almost 100 databases, and so there would end up being at least as many SQL Agent jobs, and twice that many on the secondary server.
It would be much easier to manage if log shipping could be configured to work on multiple databases.
Does anyone know of a way to do this in SQL Server, or can suggest a 3rd party tool that can do this?
October 5, 2010 at 11:17 am
You could create something, but the various steps would then be bound together. Having 100 jobs isn't necessarily a problem for SQL Agent. You could have collisions on timing, and might need more hardware to handle the load, however that would still be the case with fewer jobs. They would still take roughly the same time to run, and a failure on one database job could prevent your log shipping from working.
In my mind, I'd rather have a complicated admin setup and have some databases be protected even if others were failing.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply