Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cclabaugh
Starting Member
2 Posts |
 Posted - 2008-12-11 : 10:39:51
|
| I could use some suggestions on this:We have a web-based database application that we need to duplicate onto two other servers for various reasons to adhere to internal business practices. The database is on SQL SERVER 2005 Standard. What we'd like to do is to be able to be able to have a master database that we make schema changes to and have those changes replicate out to two other SQL SERVER 2005 databases w/o losing the data that's on them so we don't have to manually run sql scripts on them each time we make a change.What's the best method of replication/mirroring/etc to get this done?We can set up replication but have alot of changes that are always being done to the DB and would rather not have to constantly drop/add tables, etc to the replication. We'd rather not have to keep the data itself in the master db if we don't have to. |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2008-12-11 : 10:54:53
|
| Is someone going to be using the other server? If not, logshipping or mirroring is your option.Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
 |
|
|
cclabaugh
Starting Member
2 Posts |
Posted - 2008-12-11 : 11:03:21
|
| Server1 & server2 will each be on different servers that connect to their own copy of the web application. Each db should have it's own data in it and not the data from the other webserver or the master database. Server1 and Server2 will both be live websites/databases that will have their data served from the sql database on that server. Website admins will be able to login and update that data via their browsers(w/logins).At least... that's the goal. If it's not possible to do w/o having a master copy of the data in the master db then we'll go that route but we didn't really want to do that. The whole goal is to just be able to update the structure of the db in a master database and apply that automatically to the child sql servers w/o them losing their data.With regards to mirroring: we started looking at this option this week. Can it be set so that the web application (via a db connection) can pull it's data from the MIRROR while the mirror is active? I didn't see a way to do that. |
|
|
|
petek
Posting Yak Master
192 Posts |
Posted - 2009-01-02 : 07:03:14
|
| hi mate ,have you tried two way transational replication between the servers? it could do what you want.Kind RegardsPete. |
|
|
|
|
|
|
Database application replication/duplication