SQL Server Backup and Restore questions
-
Hi all, I need to make a copy of a SQL Server (2000, I think) database and a friend told me the easiest way to do this was to back up the database and then restore it to a different name. Does anyone know a good source for a step by step guide on how to do this? The database I have to back up is a production database and then I'm going to restore it to a different name to make a test copy of it and I'm just nervous working with production stuff. So a step by step guide would be very helpful. Also... if the hosting provider is backing up the server every night, does that also back up the SQL Server database? I'm just wondering if I need to tell him some specific steps to backing up the database, but if backing up the whole server does the trick then I don't need to. Thanks!
Denise "Hypermommy" Duggan
-
Hi all, I need to make a copy of a SQL Server (2000, I think) database and a friend told me the easiest way to do this was to back up the database and then restore it to a different name. Does anyone know a good source for a step by step guide on how to do this? The database I have to back up is a production database and then I'm going to restore it to a different name to make a test copy of it and I'm just nervous working with production stuff. So a step by step guide would be very helpful. Also... if the hosting provider is backing up the server every night, does that also back up the SQL Server database? I'm just wondering if I need to tell him some specific steps to backing up the database, but if backing up the whole server does the trick then I don't need to. Thanks!
Denise "Hypermommy" Duggan
Hypermommy wrote:
The database I have to back up is a production database and then I'm going to restore it to a different name to make a test copy of it and I'm just nervous working with production stuff.
You should be restoring it onto a non-production server. That way you are isolated from the production server and it would be near impossible to damage the production system while you were working on your newly created test/development system.
Hypermommy wrote:
Also... if the hosting provider is backing up the server every night, does that also back up the SQL Server database?
Most likely, but that is a question for your hosting provider. SQL Backups work differently from file backups because the SQL Server will be on-line and modifying its files. The hosting provider would have to be taking specific SQL backups. They are likely to be doing this already.
-
Hypermommy wrote:
The database I have to back up is a production database and then I'm going to restore it to a different name to make a test copy of it and I'm just nervous working with production stuff.
You should be restoring it onto a non-production server. That way you are isolated from the production server and it would be near impossible to damage the production system while you were working on your newly created test/development system.
Hypermommy wrote:
Also... if the hosting provider is backing up the server every night, does that also back up the SQL Server database?
Most likely, but that is a question for your hosting provider. SQL Backups work differently from file backups because the SQL Server will be on-line and modifying its files. The hosting provider would have to be taking specific SQL backups. They are likely to be doing this already.
I appreciate it. Yes, ideally I'd be using a different server. Unfortunately, with this client that's not do-able. It's something I hope to be able to convince them of the necessity of in the future but for now..... As far as SQL Server being backed up... I doubt it. If they have to do something different from a regular Windows backup then I don't believe it's happening. Just something else I need to talk to them about. Figuring that the hosting provider (a small company) is not doing a separate SQL Server backup, is it possible to point me to some quick literature of just a couple pages that I could send him to say "do this"?
Denise "Hypermommy" Duggan