| Author |
 Topic  |
|
|
Warlocks
Starting Member
16 Posts |
 Posted - 12 October 2007 : 19:01:30
|
I've searched, hopefully a good one, and can't seem to find my answer.
I'm pretty new at this and like to know step by step how to make a backup of my database.
We're running MS Sql Server 2005
It's on a server run by a member of our forum and I have complete access to it. I've been doing mods on our forum and although I make clean copies of the asp files I'm unable to backup our db. The guy who runs these for us and is a member of our gaming group doesn't know himself and hasn't been able to ask his 'person'.
Is there a simple process to doing this?
Thanks,
War |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 13 October 2007 : 05:33:49
|
| You need to do it using SQL Server Management Studio. The backup will need to be done to a local or networked disk, so you won't be able to your own disk. You can use the Export Wizard to export the data to a local installation, which could even be a SQL Server express edition version. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
|
Warlocks
Starting Member
16 Posts |
Posted - 13 October 2007 : 12:26:13
|
Thank you. As luck has it that's what I'm using to restart our forums on occasions when they get slow.
I have a couple of questions regarding this and another related subject.
To make a backup, is it as simple as being in SQL Server Mgt Studio / Object Explorer / Databases / Right click on desired db / tasks / backup ... ?? Once I get this far is there anything important regarding the next step I need to do, besides baking to a local or networked disk?
My second question is that in another part of this forum I've been discussing my need to upgrade from 05 to 06 on the versions. Unfortunately the guy who initially downloaded and set up the forums doesn't have the necessary information either for copying and backing up the db. When he created our forums he copied the actual forum and renamed it (for testing mods) but kept both pointing towards the same db.
Whenever I install new mods I put them up on the test forums first but again these share the same db so while the effects of the new mod arn't really felt on the live forums the posts and such from the test forum transfer easily becuase of the shared database.
How can I copy our database and use that as a true test enviorment without effecting our live forums. If I can do this then I can also spend as much time as I need upgrading from 05 to 06 and then re-doing the mods (that's gonna stink) one at a time. Once all is finished and I know the upgrading runs fine I can just switch it all back, I hope.
Thanks for the help.
War |
Edited by - Warlocks on 13 October 2007 12:28:20 |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 13 October 2007 : 12:37:42
|
That backup option will create a backup local to the database server, not your computer, so the 2nd method is preferred.
Actually you can also use the Copy Database wizard, both to backup and create the copy, so have a go at that. You can access the wizard by right clicking a DB and choosing Tasks->Copy Database. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
pdrg
Support Moderator
United Kingdom
2897 Posts |
Posted - 14 October 2007 : 10:20:03
|
You *could* (not suggested for a newcomer, but more experienced hands might like to know) also
*make the db single user/dbo only
*detach the database
*copy the mdf (forget the ldf - if you've detached the db as dbo single user, there will be no pending transactions) using windows or better still find a copy of robocopy in the Win2KS resource pack and use that
*re-attach the original mdf (the ldf will be recreated if missing/deleted)
*unset single user/dbo only
It's a very quick and robust way to move databases between servers, but make sure the SQL servers are identical versions, identical collations etc or you may hit problems (for instance SP3 on MSSQL2K would fail to load the SP2 files successfully - other versions may or may not cause problems). Ditching the .ldf is only suggested if you *know* your data and database, and make sure there aren't outstanding transactions, scheduled jobs, etc., first. If the server is a part of a live COM+ style application, this is where using MSMQ will add massive robustness and not kill your entire app by taking the db offline for 10 mins! |
|
|
| |
Topic |
|
Topic Locked
