Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
waterduck
Aged Yak Warrior
982 Posts |
 Posted - 2012-05-16 : 04:43:06
|
| Dear a,Suddenly got an idea come to mind, why need to perform database backup instead of (detach the db, copy and paste it, zip it and of cause all with .ldf).in this case wouldn't it be faster in term of back and restore.Sorry, i know this might seem silly to many of you.duck |
|
|
Sachin.Nand
2937 Posts |
Posted - 2012-05-16 : 04:57:06
|
| Detaching DB -- Your DB will be offline till you copy paste the files.Not practical at all in 24/7 environment.Copy and paste -- Imagine having a 100 GB data file and log file double that size.Backups -- Can have Compressed backups so overall backup size reduces which helps the transfer of backup files. Can have Point In Time restore with backups. Most important your based DB will be online.After Monday and Tuesday even the calendar says W T F .... |
 |
|
|
waterduck
Aged Yak Warrior
982 Posts |
Posted - 2012-05-16 : 05:08:06
|
| Hi,My environment was 9am-530pm, other than that it will be ghost, and yes my db was around that size but the .ldf was shrink to 500kb+-. I don't need any point in time restore due to my insert/update/delete was done at 5am; no more insert/update/delete will be perform until another day. No one was allow to do anything to the server other than 5am. The database was for selected statement only.duck |
|
|
|
|
|
|
db Backup vs (Detach & zip)