July 7, 2009 at 8:14 am
Log shipping works fine under bulk-logged recovery model as well.
Remember that in bulk logged recovery model, bulk operations are 'minimally' logged which means space consumed by your log file will be lesser, however the log backup will contain all extents changed by the bulk operation, hence the size of the log backups will be huge.
But this is no constraint for log shipping.
July 7, 2009 at 8:18 am
Also, do you really need to do reindexing on a daily basis? Cant you schedule it to run only during weekends when the activity on the db server is minimal?
July 7, 2009 at 8:30 am
On the log files not shrinking, there is a script on this site (Forcibly shrink[/url]) that cycles through transactions and clears the virual files, moving them to the beginning and letting you shrink.
However, don't do this is you can avoid it. If the files are going to grow again, you aren't helping.
Second, it sounds like you have issues with logs filling somehow. If that's the case, then either you don't really have log backups occurring, or you need more space. If this is important, get more space. It's not that expensive these days, and I bet a loss of trading time could easily justify another 100GB of space. What if you're sick or late one day? Car accident? It's dumb to have someone arguing over a minor expenditure.
However, figure out what you can do differently. As mentioned, check and see if you really need to reindex every day. If there isn't significant fragmentation, or you don't need a low fillfactor for some reason because of page splits, this does not help performance.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply