Connecting to Sql server 2005 via VPN

[steve]

Hi All

Has anybody had experience connecting to SQL server 2005 on a remote site
via VPN

A client has a warehouse in each capital city in Australia and wants to have
them all record sales etc in the SQL server computer running in 1 city only

I have not had experience with VPN and am wondering if the speed is
acceptable and any pitfalls to look for

I will probably be doing a once or twice daily dump of data from each local
SQL server to the coporate main one rather than per transaction

Regards
Steve

[Spam Catcher]

"steve" <ga*****@newsgroups.nospamwrote in
news:#n**************@TK2MSFTNGP04.phx.gbl:

Hi All

Has anybody had experience connecting to SQL server 2005 on a remote
site via VPN

There should be no different versus a standard LAN/Internet connection.

I have not had experience with VPN and am wondering if the speed is
acceptable and any pitfalls to look for

Speed is fine... if you have enough bandwidth. The performance is also
dependent on how much data will be travelling across the WAN.

Depending on your application, you may want to front the DB access with
a centralized web service instead - rather than having direct DB
connections.

I will probably be doing a once or twice daily dump of data from each
local SQL server to the coporate main one rather than per transaction

If you're planning on using a local DB at each site and syncing to a
central database, SQL Server has the capability built-in to do so (Log
shipping and Replication). However, there are several third party
products which do it better (DoubleTake, WANsync, etc)... and are
definately worth a look. Try the SQL newsgroup, people there can give
you some recommended products to compare.

In anycase, there are several ways you can tackle this problem. Either
sync the database up, or you could build an application framework to do
the syncing for you. If all you want is database syncing, I would do it
with SQL Server (or use a 3rd party SQL server product).

[steve]

Spam Catcher

Thanks for your reply

Just what I needed

Regards
Steve
"Spam Catcher" <sp**********@rogers.comwrote in message
news:Xn*********************************@127.0.0.1 ...

"steve" <ga*****@newsgroups.nospamwrote in
news:#n**************@TK2MSFTNGP04.phx.gbl:

>Hi All

Has anybody had experience connecting to SQL server 2005 on a remote
site via VPN

There should be no different versus a standard LAN/Internet connection.

>I have not had experience with VPN and am wondering if the speed is
acceptable and any pitfalls to look for

Speed is fine... if you have enough bandwidth. The performance is also
dependent on how much data will be travelling across the WAN.

Depending on your application, you may want to front the DB access with
a centralized web service instead - rather than having direct DB
connections.

>I will probably be doing a once or twice daily dump of data from each
local SQL server to the coporate main one rather than per transaction

If you're planning on using a local DB at each site and syncing to a
central database, SQL Server has the capability built-in to do so (Log
shipping and Replication). However, there are several third party
products which do it better (DoubleTake, WANsync, etc)... and are
definately worth a look. Try the SQL newsgroup, people there can give
you some recommended products to compare.

In anycase, there are several ways you can tackle this problem. Either
sync the database up, or you could build an application framework to do
the syncing for you. If all you want is database syncing, I would do it
with SQL Server (or use a 3rd party SQL server product).