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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-07-08 : 08:40:12
|
| Lewie writes "I am trying to work out which is the better way to go between transaction/merge or log shipping in my particular problem.The application is a client/server banking system with +- 1000 users, SQL2000 and windows 2000. The main server sits at a hosting sight but management would also like another server off sight that is up-to-date as much as possible should there be a disaster. Also, a report sever must get a copy of the database once a night for the next days reporting. Batch processes occur on the main server in the evenings. Some questions I have are, if I choose immediate transaction replication can the user go onto the replicated server and continue working should the main server fail. The system could be resynchronizes at a later stage when all is well with some effort. Transaction replication will allow reads from the replicated server reducing the read requirement on the main server thus improving performance. Merge replication could be a problem if I allow user to work on both servers and the link is lost. The batch would end up calculating values on incorrect amounts resulting in days of sorting out balancing issues on difference customer’s accounts.Which is the best for performance and should I use a separate server for the distribution?Sorry, maybe too many questions." |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-07-08 : 12:26:50
|
| Replication is not designed to be used for disaster recovery. You will want to use Log Shipping. If, when you set up your log shipping, you restore the full Backup 'with Standby' it will be read only, which you can offload some of the read traffic to.-Chad |
 |
|
|
|
|
|
Which Replication