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 |
|
Jaapie
Starting Member
7 Posts |
 Posted - 2005-05-17 : 06:16:57
|
| Hi,We have a central live DB that supplies data to multiple web applications. This database has a heavy write load as well from multiple incoming feeds. We are have a performance issue as you can imagine.I was thinking of having a DB that production writes to and a seperate DB that the Web apps read from. Our data is fairly real time and 24 x 7 so its not ideal to batch upload changes.Was looking at SQL transactional replication. Would this solve the issue. Is the insert at subscriber equal the same overhead as insert on the publisher. Is there a better way of looking at this.This surely is a typical issue for a online 24 x 7 app ?thanks |
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2005-05-17 : 07:25:17
|
| Log shipping will provide for what you require, so long as your web apps can afford the few moments offline whilst the logs are applied (which can be at intervals of your choosing)-------Moo. :) |
 |
|
|
|
|
|
Seperate read and write DB