Comments
Sort by recent activity
Thanks Robert. I bookmarked the blog for future reference. So far my HDD space seems to be back to the normal incremental creep now that I switched to BULK-LOGGED. In my case, my primary databases are live databases with data entry and input always available, and the secondary databases are all on standby in read-only mode, so that I can restore log files daily. Seems to work well for me.
Thanks again for the help.
Hugh / comments
Thanks Robert. I bookmarked the blog for future reference. So far my HDD space seems to be back to the normal incremental creep now that I switched to BULK-LOGGED. In my case, my primary databas...
I am switching from FULL to BULK-LOGGED recovery type to see it that fixes my problem tonight. I am doing a huge data load on all these databases every night. These databases are basically table copies of legacy data that are deleted and repopulated every night. Then I am using log shipping so these same databases can be available on the reporting server as well.
My main problem is I can't get a handle on what you can and can't do to maintain your log size without breaking the log shipping chain.
It is a mess but I'm getting close. Thanks. / comments
I am switching from FULL to BULK-LOGGED recovery type to see it that fixes my problem tonight. I am doing a huge data load on all these databases every night. These databases are basically table ...
Thanks Jason. It was just the size of my variable. Because it is varchar rather than char, I'm not sure why that would cause the SP to not work but hey, it works now. That's what counts.
I appreciate your help.
Hugh / comments
Thanks Jason. It was just the size of my variable. Because it is varchar rather than char, I'm not sure why that would cause the SP to not work but hey, it works now. That's what counts.
I appre...