Quote:
Originally Posted by shalym
I also "do this stuff for a living", and in the real world, most databases are NOT shut down every night so that a backup can be done. Most *modern* backup programs can and do handle database backups without completely shutting down the program and without corruption. I maintain several MS SQL and MySQL databases that are backed up every night, with test restores done at least monthly, and I can tell you that I've never had a backup corrupted because a database was open while it was being backed up.
Shari
|
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.