Olympic Games Support in Torino 2006

We are utilizing a .net front end Client side application to access a remote
SQL database. We will be using this method for transactions locally to issue
apparel to Athletes as well as other information about our team. The
question I have is our proposed setup is to have a 2MB line using a VPN
connection back to our home site and conduct live application entry, we will
then have a local client facing server in Italy for disaster recovery
performing stored procedures to trigger replication for a backup copy. We
proposed this topology as other members need real time access to the data at
multiple locations. Are main concerns are survivability of the database and
potential latency issues over a leased line. Anyone have any thoughts?
I wouldn't use stored procedures for that but setup replication.
In case the link fails you have disconnected systems that can operate
independent from eachother and when the connection comes back up replication
will occur.
There are several replication topologies and methods possible.
This will depend on the amount of data you want to replicate as well.
Thinking of snapshot replication or transactional replication
Probably transactional with immediate updating subscribers might be the
option.
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"Paul Walker" <Paul Walker@.discussions.microsoft.com> wrote in message
news:5488F052-E627-415C-AD93-545D726BA28F@.microsoft.com...
> We are utilizing a .net front end Client side application to access a
> remote
> SQL database. We will be using this method for transactions locally to
> issue
> apparel to Athletes as well as other information about our team. The
> question I have is our proposed setup is to have a 2MB line using a VPN
> connection back to our home site and conduct live application entry, we
> will
> then have a local client facing server in Italy for disaster recovery
> performing stored procedures to trigger replication for a backup copy. We
> proposed this topology as other members need real time access to the data
> at
> multiple locations. Are main concerns are survivability of the database
> and
> potential latency issues over a leased line. Anyone have any thoughts?