SQL backup or replication?

Question

I have a SQL server that has a test pp I have written. This thing is gaining traction and I am worried about losing data (and the time it took users to enter the data) if the SQL server gets corrupted or someone does something dumb.

I am thinking of what options I have that would do a nightly backup as a maintenance plan, and what I can do as far as replicate the DB to another SQL server box.

What are the pros and cons? What's the best practice here?

score 0 · Accepted Answer · answered Sep 15 '10 at 18:44

0

If you only need to preserve the structure and contents of the database, then the database backup is best.

If you have a need to work with a replica of the database, then consider replication. Replication takes more work to maintain, and doesn't provide an easy recovery capability if it's there only for backup reasons.

answered Sep 15 '10 at 18:44

bobs

21,844
12
67
78

any word on how i can get a daily job to backup the DB and all its data twice daily? – kacalapy Sep 15 '10 at 18:49
You can create an SQL Server scheduled job that launches the backup. There are a couple of ways to schedule this job twice a day. For example, you can schedule it to run every 12 hours and set the time it first runs. – bobs Sep 15 '10 at 19:21

score 0 · Answer 2 · edited May 23 '17 at 12:29

0

Automated backups answered here.

edited May 23 '17 at 12:29

Community

1
1

answered Sep 15 '10 at 19:06

Bernard

7,908
2
36
33

score 0 · Answer 3 · edited Apr 13 '17 at 12:13

0

I guess you should combine full backups + transation log backups.
This kind of question should be made on serverfault.com - In fact there is a similar question here.

edited Apr 13 '17 at 12:13

Community

1
1

answered Sep 15 '10 at 19:08

rsenna

11,775
1
54
60

score 0 · Answer 4 · answered Sep 15 '10 at 20:10

Daily full backup is the Best. If the database size is small, you dont need to keep a replica, since the restore time is less. If its a large database you can consider logshipping or mirroring . For these you need to have the database in full recovery model and have to setup transaction log backup at regular interval. Replication is useful only if you are interested only few tables and not the entire database and it will be transactional replication int his case. Maintenance plan wizard is helpful to set up regular full backup as well as transaction log backup.

score 0 · Answer 5 · answered Oct 19 '10 at 17:54

You can try Web Deploy tool, which is free and powerful for a lot of tasks.

All you need to do is to use DbFullSql provider and specify a connection string for a source and a file for destination. Web Deploy will use SMO to script your database to a file:

Backup db schema and data:
>msdeploy.exe -verb:sync -source:DbFullSql="Server=.\SQLExpress;Database=MyDatabase;Integrated Security=true" -dest:dbfullsql="d:\DbBackup.sql"

Backup just data (set ScriptData properties as shown in this article):
>msdeploy.exe -verb:sync -source:DbFullSql="Server=.\SQLExpress;Database=MyDatabase;Integrated Security=true",ScriptSchema=false,ScriptData=true,ScriptDrops=false -dest:dbfullsql="d:\DbBackup.sql"

SQL backup or replication?

5 Answers5