Options
Backup Publication information?
BVAN
Posts: 3
We are replacing some of our SQL boxes with entirely new servers. We have backups of all the databases done with full and log ships.
We are running SQL Server 2000 and Redgate SQL Backup 5.3.0.178
A problem was posed to me from a couple of our developers that we have very unique information in the publications that allow our users with handhelds to connect.
Is there a way that I can transfer the publication info from Server A to Server B?
If I cannot find a way to do this, each handheld user (500 of them) will need to download an entirely new database, then taxing the performance of my new SQL box that is supposed to be fixing my bottleneck issues.
If this isnt making enough sense, I apologize. I am very new to SQL and SQL Backup.
We are running SQL Server 2000 and Redgate SQL Backup 5.3.0.178
A problem was posed to me from a couple of our developers that we have very unique information in the publications that allow our users with handhelds to connect.
Is there a way that I can transfer the publication info from Server A to Server B?
If I cannot find a way to do this, each handheld user (500 of them) will need to download an entirely new database, then taxing the performance of my new SQL box that is supposed to be fixing my bottleneck issues.
If this isnt making enough sense, I apologize. I am very new to SQL and SQL Backup.
Comments
Sorry for the delay in replying back to you.
With regards to the transfer of your publication info. If this information is in a database? Then you can use SQL Backup to backup the database and restore onto the new server.
Otherwise I need further details on the publications information you are looking to transfer?
At this time we do not have an application that supports handheld devices.
Many Thanks
Eddie
Senior Product Support Engineer
Redgate Software Ltd
Email: support@red-gate.com
A publication to a replicated database is at the server level this does not re-store with a backup. You have to script out the publication and run it against the new server. When you do this it initializes all client databases and all of our users must delete their database and get a new one.
There may be a way around for this but I do not know if there is.
It appears that I will not be able to use SQLBackup to do this.
SQL Backup Consultant Developer
Associate, Yohz Software
Beyond compression - SQL Backup goodies under the hood, updated for version 8