Transfere data from branch to branch backup small size

[ahm1985]

I have 2 branches database A,B same structure and objects different only in data i must take backup every day.but i face problem Differential backup is big and when i compress also is big so that when i send him by email it will not accept because it is big how i send it small size as possible
Notes
sql server 2005 in two branches
we cannot make replication because the two branches are not connected online(location in dessert and slow disconnected more time)
email only available can i send transaction that make every day to all database
by backup(in small size)
when i take full backup from database it is 1.5 g.b and differential is 800 mb

 

[SQLScholar]

That differential seems rather large!

How often are you doing a full backup? Remember a differential is everything that has changed since the last full backup. So effectively you will need to ship a full backup occasionally. Basically there is no way to get round this without doing a full backup once in a while.

----------------------------------------

http://www.fountain.me.uk

Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Bernard Baruch

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------

 

[SQLBill]

To further explain what SQLScholar is saying....

Let's say you took a Full Backup at midnight on 1 March. Then on March 2nd you make a differential, that differential has every change made since midnight 1 March. Then on March 3rd you make a differential, that differential has every change made since midnight of 1 March. Then it just keeps going and since every differential made contains every change since 1 March, it is going to get bigger and bigger. This is why differentials can become larger than the original database.

There's no easy solution for you since you can't connect to the other sites. Probably the best would be to copy the data to a DVD and overnight it to them. If you do that, I would suggest at a minimum doing a full backup once a week and then do differential backups each day sending them via overnight delivery.

You do have to remember that once you recover the database, you can't restore another differential to it. So your users will have to restore the full backup and the new differential every day.


-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875

 

[ahm1985]

OK and after i make full backup what i will do i need only transaction backup that made every day in small size if possible
thanks

 

[SQLBill]

Again, to restore transaction logs, they have to restore every single one in order. But they can't RECOVER the database until all the transaction logs are backed up. Once you recover the database, you can't restore any more transaction logs. For the database to be usable, they would have to restore the Full Backup and all transaction logs made, then recover the database. When they got the next transaction log, they would have to restore the database, all the transaction logs and the new transaction log, then put the database into recovery.

So no matter which you do....differential or transaction log backups, they will have to restore the full backup every time along with whatever backup you send them. Once you put a database into recovery, no more backups can be applied.

If you absolutely have to do this...I suggest doing a Full Backup once a week, overnighting it to them, and then emailing them the transaction logs (if they can be made small enough). But it will require them to restore the database and tlog backups daily.


-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875