November 23, 2009 at 7:46 am
A coworker said that when you perform a backup on a database (which I do on the hour) that the que is first flushed ( all data retrieval and updates are lost) and then the backup is ran. I'm not a DBA and know little about backups but this seems a little hard to believe. Can someone confirm or direct me to some documentation that would clarify this?
November 23, 2009 at 8:46 am
incorrect.
a backup does not affect anything in process. It captures all changes that are committed up to the end of the backup, but does not lose anything.
November 23, 2009 at 10:04 am
cclancy (11/23/2009)
A coworker said that when you perform a backup on a database (which I do on the hour) that the que is first flushed ( all data retrieval and updates are lost) and then the backup is ran.
If it was so, then it would have been called flushup (instead of backup)..:-)
I suggest you to go though these links
SQL Server 2000 Backup and Restore
Also pass the links to your colleague
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 23, 2009 at 10:29 am
A backup process does not cause any lost of data or changes. It takes the backup of all the committed changes to the database during the process. Due to load on the server, during database backup activity, the other process may work slowly but does not cause any loss of data or changes.
November 23, 2009 at 11:18 am
Thanks to all:-).
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply