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 |
|
csaha
Yak Posting Veteran
52 Posts |
 Posted - 2012-08-01 : 10:37:58
|
| I am new to replication and would like to setup Replication so that when one of the database server is down, we can connect the application to another server and will be up and running in few hours. We also do a backup of the databases. I choose Transactional Replication because it is most common replication type and it tracks and replicates to the Subscriber. However while building transactional Replication, I found that I cannot create replication if there are tables without primary key. So does that mean I should look into different kind of replication? Can I build two types of replication in the same server. I have 13 databases in the server and among that I have 9 databases where the tables does not have primary key. I do not know if it is a good idea to build primary key to all those tables. Please advice. |
|
|
Transact Charlie
Master Smack Fu Yak Hacker
3451 Posts |
Posted - 2012-08-01 : 12:06:30
|
you need to have a pk to enable transactional replication. And that's probably what you want..Someone could probably advise about log shipping though if a fail over cluster is more your cup of tea?You *should* have a primary key on every table if your design is at all normalized anyway.Transact CharlieMsg 3903.. The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. http://nosqlsolution.blogspot.co.uk/ |
 |
|
|
csaha
Yak Posting Veteran
52 Posts |
Posted - 2012-08-01 : 12:30:47
|
| If I create primary key to all table because I have quiet a few tables, will it cause any performance issue? Is transactional replication my best choice? What about snapshot, or merge replication. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2012-08-01 : 13:32:07
|
| If you intend to WRITE to the failover instance in a disaster, then I'd suggest database mirroring or log shipping.Also have a look at failover clustering |
|
|
|
|
|
|
Replication of sqlserver 2008R2 server