hundreds of databases sql server log shipping

Posted by Oliver on Stack Overflow See other posts from Stack Overflow or by Oliver
Published on 2010-03-29T18:33:59Z Indexed on 2010/03/29 19:23 UTC
Read the original article Hit count: 452

Filed under:
|

SQL Server 2005 Standard 64x, with 300+ tiny databases currently (5MB each), user base adds databases as needed. Want to implement log shipping for warm standby, but not via the wizard, since that looks like it adds 3 jobs (1 on primary, 2 on secondary) for each log-shipped database.

Do I try to write my own or use something like Quest's LiteSpeed? Or am I being too squeamish about having hundreds of SQL Server Agent jobs and all of them firing off (or worse, would I have to try to time them)?

All advice welcome.

© Stack Overflow or respective owner

Related posts about sql-server

Related posts about log-shipping