InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 07:44:44 GMT20http://www.sqlservercentral.com/Forums/Topic1398315-361-1.aspxJust a thought, I would also keep and stash away a copy of the associated logins scripted out using the sp_help_revlogin procedure. That way, you can reinstall the database on another server if needed, and it will keep the same security ID's for the logins, and any SQL Authentication passwords.Thu, 20 Dec 2012 08:20:35 GMTvikingDBAhttp://www.sqlservercentral.com/Forums/Topic1398315-361-1.aspxThat simple eh...Thanks!RaymondWed, 19 Dec 2012 05:28:33 GMTRaymond van Laakehttp://www.sqlservercentral.com/Forums/Topic1398315-361-1.aspxWhy not just drop the database after you have backed it up?Wed, 19 Dec 2012 05:02:00 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1398315-361-1.aspxHey,Each of my customers has his own database. Sometimes a customer quits. When that happens, I want to archive that database. My idea is:1) Make a full backup to "\\backupserver\final_backups\FINAL_BACKUP_CUSTOMERNAME.BAK"2) Detach the database "DBCUSTOMER"3) Delete the files DBCUSTOMER.MDF and DBCUSTOMER_LOG.LDFIs this the way to go? And if so, how do I do step 3 with T-SQL? Thanks,RaymondWed, 19 Dec 2012 04:52:30 GMTRaymond van Laake