Solved

SQL SERVER 2000 Replication over the INTERNET

Posted on 2007-03-24
5
140 Views
Last Modified: 2013-12-05
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.
0
Comment
Question by:excelclothing
  • 3
  • 2
5 Comments
 
LVL 16

Expert Comment

by:rboyd56
ID: 18785833
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
 
LVL 16

Expert Comment

by:rboyd56
ID: 18785836
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
 

Author Comment

by:excelclothing
ID: 18785854
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
 

Author Comment

by:excelclothing
ID: 18785859
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
 
LVL 16

Accepted Solution

by:
rboyd56 earned 125 total points
ID: 18786073
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

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Everyone has problem when going to load data into Data warehouse (EDW). They all need to confirm that data quality is good but they don't no how to proceed. Microsoft has provided new task within SSIS 2008 called "Data Profiler Task". It solve th…
Slowly Changing Dimension Transformation component in data task flow is very useful for us to manage and control how data changes in SSIS.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to setup several different housekeeping processes for a SQL Server.

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question