SQL SERVER 2000 Replication over the INTERNET

I have 4 retail stores. I want to write a simple login program in VB6 to enable staff to login. I have no experience with ASP and wish to use VB6 with SQL server 2000 in each store and backoffice.
So that my backoffice adminstrator and all store managers have access to the data for each store is it doable to have replication working in each store VIA the INTERNET to update all data LIVE.
excelclothingAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rboyd56Commented:
Yes you can replicate over the Internet.  About the only condition is that the respective servers have to be able to connect to each other.

If you need to update data at all sites then merge replication is probably the best bet.

One caveat is that merge will add a rowguid column with a unique identifer data type to each table if there is not a column with a unique identifer already established.

Since this is the case you will need to make sure your applications takes that into considration.
0
rboyd56Commented:
One other thing, the data will not be live, there will always be a latency period. The amount of latency is dependent on the network and other factors.
0
excelclothingAuthor Commented:
I will be coding in VB6 and using an ADO connection to each local SQL server.

There will not be a great amount of data going across the INTERNET, however is there a recommended record lock setting I should use for the connect string, ( I'm a rookie programmer, not an expert !) ?

Is it fairly easy to set up the various SQL servers to replicate to each other?

0
excelclothingAuthor Commented:
Thanks of that. Normally what time period should I expect for a latency period. Would it be in seconds or minutes for each record??
0
rboyd56Commented:
It depends on the network and the amount of data that is being replicated. Merge replication makes use of triggers and stored procedures to replicate the data. If you establish joins between the tables that are being replicated, in the publication  then it will take longer for the data to be replicated. There is no way I can give you an exact answer. There are too many variable.

Merge replication is not that difficult to set up. ONce again it depends on how complex you wan to be. Books on Line has excellent documentation on how to set it up.

As for locking, replication should have very little impact on this, so you should not have to do anything special.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.