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 |
|
mike123
Master Smack Fu Yak Hacker
1462 Posts |
Posted - 2008-02-29 : 08:49:12
|
| Hi,I have zero experience running any databases that spread further than 1 machine, so I have a few theory questions here that hopefully someone can help with. Hopefully this is the right forum, I'm not sure if it classifies as 'clustering'.Anyways, we are launching a web app that is going to start with just 1 webserver/db server. For speed reasons, after some growth we might have to have a load balanced setup with a webserver in europe and one in north america. Basically the webservers are going to be serving 100,000's of files and each time a file is served it needs to be recorded in the database.I think that if I'm connecting my european webserver across the internet to my db server, thats killing the purpose of having a webserver in europe to make for faster responses.I am thinking that this european web server/db serving is only going to be logging the files served. Is there a way to import them into north american database everynight ? I'm not sure what the best approach would be for something like this, but any suggestions are greatly appreciated. Thanks very much,mike123 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-02-29 : 09:31:00
|
| Check out Peer-to Peer Replication in SQL server 2005 |
 |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2008-02-29 : 09:31:06
|
| Having a single database server that serves both US/Europe webservers would kill the performance of the website so having one database present at each site is essential. Migrating data between them can be done in a number of ways where replication or log shipping would be the most common ways.--Lumbago"SELECT Rum, Coke, Lime, Ice FROM bar WHERE ClosingTime = 'Late' AND FemaleMaleRatio > 4" |
 |
|
|
|
|
|
|
|