Quote:
Originally Posted by HarryT
But you presumably do your database backups using the backup facilities of MS SQL Server itself (just as I do), not by simply copying the underlying file system files. If you use the backup facility of the database itself, then yes, it does it properly, no argument about that, and no need to shut anything down. But that's not what we're talking about in this situation: it is assuredly not safe to simply copy the files of an open database. You might get away with it 9 times out of 10, or even 99 times out of a hundred, but sooner or later you'll hit problems when you have pending transactions that haven't been committed to the database.
|
It depends on the solution. For some, yes, that is the procedure. For others, the database backup script is included in the main backup script for the server. I'm just saying that making a blanket statement of "backing up an open database will cause corruption" isn't necessarily true. If it were, then most mail servers wouldn't be backed up, and neither would most websites--these days most websites have at least one component that is completely dependent on a database, and also need 24/7 uptime.
Shari