Deploying a database to multiple servers - smooth sailing?

Hello,
I need to copy a database to multiple servers, all of this using SQL Server
2000. -- this will enable the testing of an application with identical
databases. I'm concerned here with the original installation of the database
on the target servers and subsequent updates using restoration of the
database from the master server
I'm contemplating having the master database on one server and using data
management objects to make a database backup on that machine. That backed-up
database would be placed in a share with some scripts that would perform the
restore on the target servers - to be initiated by the users.
This works well on my master server but can I expect a smooth distribution
using this approach or is there a better approach. I like this method as
it's simple. The target servers will all be SQL Server 2000, possibly with
different service patches. The target servers would has the same local
administrators account.
Is there anything internal to the back up or the target server that would
prevent this operation? There's no dependencies such as a database can only
be restored to a server it was backed up on, is there?
TIA,
Rod> This works well on my master server but can I expect a smooth distribution
> using this approach or is there a better approach. I like this method as
> it's simple. The target servers will all be SQL Server 2000, possibly
> with
> different service patches. The target servers would has the same local
> administrators account.
Your servers should all be at the same patch level. Occassionally, there
are differences in the structure of the backup that are not backward
compatible.
> Is there anything internal to the back up or the target server that would
> prevent this operation? There's no dependencies such as a database can
> only
> be restored to a server it was backed up on, is there?
No.|||Thank you
"Scott Morris" wrote:
> > This works well on my master server but can I expect a smooth distribution
> > using this approach or is there a better approach. I like this method as
> > it's simple. The target servers will all be SQL Server 2000, possibly
> > with
> > different service patches. The target servers would has the same local
> > administrators account.
> Your servers should all be at the same patch level. Occassionally, there
> are differences in the structure of the backup that are not backward
> compatible.
> > Is there anything internal to the back up or the target server that would
> > prevent this operation? There's no dependencies such as a database can
> > only
> > be restored to a server it was backed up on, is there?
> No.
>
>