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 |
|
ragalante
Starting Member
1 Post |
 Posted - 2011-01-27 : 14:46:37
|
| Hey, I have a big database in sql server 2005, and since it´s so big I need to replicate it to other sever. I set up sql replication publisher and subscriptor but it doesn´t behave in a stable way. It´s not replicating for every insert and it´s not throwing any exceptions either. Also, I´m concerned about performance here, so I was wondering if maybe there is some other alternative I could use... I don´t need to replicate every row in the database, or all the tables either.UPDATE: What I´m trying to achieve here is a load balance for the database. I expect a lot of traffic here, so I´m thinking using the replicated databse to show information to users. Meaning, inserts, updates and deletes will be performed in main databse, and selects will be performed in the new databse. Since the replicated databse will be just for selects, and show information to users, I just need those rows that are active for the app. Also, I´m thinking of having not normalized tables here, to avoid using joins and retrieve the information as fast as I can. the replication I set up is transactional, and really, the problems I have is that following the same process to insert a row, it once replicate the result, and then tryed again and it didn´t. And it has been working like that since.Any comment or suggestion will be appreciated!Thanks! |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-01-27 : 15:15:29
|
| You've done something wrong. Replication is very stable. Query distribution..msrepl_errors to view error messages, also check SQL error logs. |
 |
|
|
|
|
|
|
|
Transactional replication not working stable