July 17, 2007 at 11:20 am
Hi Guys,
Can anyone confirm for me if there is any hard limits in terms of the number of DBs and/or servers that can participate in log shipping. I have 64 DBs that are setup for log shipping. These are across 2-3 production and 2-3 DR servers. I'm using one server as the monitor for all of these.
BTW, does this setup qualify me for the log shipping "hall of fame?" 😉
Thanks in advance,
Tushar
July 17, 2007 at 7:06 pm
Not sure about any limitation with the inbuilt Log Shipping. As a rule we don't use the inbuilt log shipping we prefer to use our own T-SQL scripts and have each step isolated to avoid any delays. eg: waiting for backups to occur while large file is transferred to standby location.
The most we have running on one server is 21 DBs.
Given that Log Shipping is basically a backup, copy and restore. You can break these into seperate scheduled jobs that run as frequently as required. You can even break the individual steps up into multiples if you want to group DBs together, or have a DB that requires a little extra attention.
This gives you flexibility to arrange each of the tasks to meet whatever your requirements would be. eg: some DBs on a more frequent schedule, pause restores without losing backups and needing to re-initialise, ...
--------------------
Colt 45 - the original point and click interface
July 18, 2007 at 7:00 am
Thanks Phil.
Our company is just starting to put together a DR plan for our SQL DBs and we're using the internal log shipping as an easy way to get something in place. As we become more comfortable with the DR environment we'll most likely create custom T-SQL scripts that accomplish the same.
Based on other research that I've done, I haven't been able to find any technical limits in terms of the number of DBs and servers that can participate in log shipping. I'll just watch all the servers and ensure that we're not exceeding the hardware capabilities.
July 18, 2007 at 7:58 am
There is no constraint of number of databases that can be used in log shipping in a single server. But the server hardware and network should hold desirable limits to do good to your performance. implementing log shipping should not spoil the network and server performance.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 18, 2007 at 10:14 am
Thanks for confirming my intuition Sugesh. I'll monitor the server hardware and network utilization to avoid any possible problems.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply