Comments
Sort by recent activity
Much appreciated. SQL 2008 R2. Currently there is 172MB available, so I can see now that anything over 6 concurrent restores at a time would be problematic. Based on this I know I can go up a small amount on the VAS and be perfectly safe.
Thanks for the information > on to a bit more fine tuning. [image] / comments
Much appreciated. SQL 2008 R2. Currently there is 172MB available, so I can see now that anything over 6 concurrent restores at a time would be problematic. Based on this I know I can go up a sm...
What are the side effects of lowering the maxtransfersize? Would this increase time to complete each restore only, or are there are things to consider here?
Thanks for the insight / comments
What are the side effects of lowering the maxtransfersize? Would this increase time to complete each restore only, or are there are things to consider here?
Thanks for the insight
From looking at the -g option I can see the benefits of using it. I took a closer look on MSDN: http://msdn.microsoft.com/en-us/library/ms190737.aspx
The only thing I'm a bit hesitant to do is to increase this too much. As it appears that I have alleviated the issue by staggering my processes it may be fine. As there is so much of our business running on the SQL databases I'm a bit hesitant to make many changes like this without understanding the upper and lower limits and what the possible issues I might see are. / comments
From looking at the -g option I can see the benefits of using it. I took a closer look on MSDN: http://msdn.microsoft.com/en-us/library/ms190737.aspx
The only thing I'm a bit hesitant to do is to...
For anyone else that runs into this issue I have found a work around for my scenario. It may actually be a better set up in the long run as it allows for fewer processes at a time.
I have gone in and staggered my restores to occur at two minute intervals so that there are never any more than 3 log shipping jobs attempting to occur at a time. It's taken a bit of fine tuning and I'll have to watch it over the next few days/weeks to be sure I got it. Ultimately with the number of databases that I have it's almost a continuous string of restores that are being done.
If anyone has any thoughts please contribute them! [image] / comments
For anyone else that runs into this issue I have found a work around for my scenario. It may actually be a better set up in the long run as it allows for fewer processes at a time.
I have gone in ...
Is there any resolution to this? I am not all that interested in going in and modifying each of my scripts manually. I have 28 databases that are configured for log shipping. Unlike many SQL administrators I can't sit and monitor or waste a lot of time with SQL.
I have found through increasing notification that this is the exact scenario that has caused me to lose many of my log shipped databases.
Ignore this.. creating a new thread. / comments
Is there any resolution to this? I am not all that interested in going in and modifying each of my scripts manually. I have 28 databases that are configured for log shipping. Unlike many SQL adm...