Home/ Questions/Q 699031
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T03:20:27+00:00

SQL Server 2005 Standard 64x, with 300+ tiny databases currently (5MB each), user base

  • 0

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.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Since you provision a new database per user, I would advice against the built in Lo Shipping. With each newly provisioned db you’d have to add a new Log Shipping session, jobs and all that.

    Given that Log Shipping is really trivial at it’s core (backup, copy, restore, repeat) I would consider instead an automated solution build from scratch, with fewer jobs (eg. One job cycles through backups, one copyes , one or two aplly restores).

    • 0