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 |
|
peryan77
Starting Member
8 Posts |
 Posted - 2009-07-28 : 10:51:18
|
| I am not a DBA, but rather a developer, so I need a little guidance - we have no DBAHere is my scenario, We have an office in London and in Boston. The network connection between the 2 offices suk.I created a winforms application with a sql server backend. Currently, the database is in Boston, but London is experiencing vast slowness. Thus, we need a solution, and I was thinking we could put a database in London, and set some form of replication. Btw, this is not read-only data, users are creating/editing sales forecasts and users from London and Boston can work on the same forecast (just not at the same time - application restriction - I lock a forecast when someone has it open)Now, I am not sure which replication scenario to choose (merge?) or how many servers / databases I need to set this up.Also, none of my tables use Guids, they use ints, is this going to be a problem?We have no budget for a DBA, so it looks like the burden falls on me. |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-07-28 : 14:14:02
|
| look at peer-to-peer replication.you're going to have difficulties if the internet connection is poor though. also connection should be over VPN |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-07-28 : 14:15:51
|
| ints are fine. all replicated tables need a primary key thoughalso, you're going to need to be careful with identity fields. seed them on each end so tey can't clash...for example make london odd and boston even and increment by 2 |
|
|
|
|
|
|
|
|
Which replication do I need...?