replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

sql

replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

replication failed after restart

Hi..

I've 3 pc that have MS SQL 2000 database installed in it and connected to main server through merge replication.

At first it run fine all the time. But now, it doesn't. It's happen when the pc have to restart every night. When i come to the office and check resplication status it return failed. I try to manually start synchronize but it failed too. I've to restart the pc all over again untill it ok.

I hope some body out there can explain something to me and how to overcome the problem...

If the PC restarts during the initialization then it will fail and you will have to start initialization again.

It would be helpful to know the error messages.

Martin

|||

the error message is

the process could not connect to subscriber

|||

Can you confirm that the subscribers are up and running? After a reboot are the SQL Services all started and the databases available?

|||

yes...|||

Instead of restarting the pc, did you try connecting to the subscriber via isqlw, osql.exe or some other client tool with the same credentials that the merge agent uses? If that also fails then it's not replication.

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson
"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evaluat...eplication.asp
Steve

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson
"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evaluat...eplication.asp
Steve

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson
"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evaluat...eplication.asp
Steve
sql

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evalua...replication.asp
Steve

Replication between never-connected SQL Servers

Is it possible to set-up replication between two servers that are never
directly connected?
We have a production server that is not connected to our network for
security reasons. I am doing testing on a local server and then want to
periodically apply the updates to the production server via CD. I haven't
been able to do this with replication as it seems to require a connection to
the subscription db for the initial snapshot.
At the moment, the only way I have been able to do this is by creating a
backup and recreating the db on the remote server.
Thanks!
James
James,
replication will require a connection between servers at some point. Where a
connection is not possible, you can use a derivative of log shipping or
database shipping as you are doing.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks very much Paul.
James
"Paul Ibison" wrote:

> James,
> replication will require a connection between servers at some point. Where a
> connection is not possible, you can use a derivative of log shipping or
> database shipping as you are doing.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>

Replication advice

Hello,
I have 30 remote WinXP sites connected to a Win 2K3 server via VPN.
Each remote site runs MSDE. Basically, they are automated data aquisition
machines recording into a DB about 200K of data every 15 minutes.
The data at each remote site needs to be replicated into its own DB on the
Win 2K3 server on a regular basis, hopefully within 1 or 2 hours of being
first recorded..
What form of replication would be recommended for this scenario?
Thank you
Unfortunately MSDE cannot be a transactional publisher which is the best fit
for what you are trying to do. What you will have to do is use merge
replication with the with the exchangetype being upload only.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"MikeH" <MikeH@.community.nospam> wrote in message
news:1AD6F4E7-B7B0-412E-BA9F-D05B7BE6168F@.microsoft.com...
> Hello,
> I have 30 remote WinXP sites connected to a Win 2K3 server via VPN.
> Each remote site runs MSDE. Basically, they are automated data aquisition
> machines recording into a DB about 200K of data every 15 minutes.
> The data at each remote site needs to be replicated into its own DB on the
> Win 2K3 server on a regular basis, hopefully within 1 or 2 hours of being
> first recorded..
> What form of replication would be recommended for this scenario?
> Thank you

Replication - will this work?

I have a system with two SQL 2K servers. The two servers are connected by
dial up 56K lines which will be used to update the system. The requirement
is that the first server S1 database match the second server S2 database on
a daily basis. S1 will be heavily updated but S2 will mostly have few
changes.
I was thinking replication via the SQL server would be the best way to
implement this but was wondering if it was possible.
One of my concerns is that since the two servers are not connected all the
time will they update correctly when they are connected.
I am also concerned about how the system will handle records that are
updated on both system and then merged.
Also can the replication occur while the server is receiving new data?
Any comments, suggestion, or links would be appreciated.
Regards,
John
John,
Merge replication should do what you need, it is designed for occasionally
disconnected sites. Check it in Books Online whether this is what you need.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"John J. Hughes II" <no@.invalid.com> wrote in message
news:ueBIwtHvEHA.1296@.TK2MSFTNGP10.phx.gbl...
> I have a system with two SQL 2K servers. The two servers are connected by
> dial up 56K lines which will be used to update the system. The
requirement
> is that the first server S1 database match the second server S2 database
on
> a daily basis. S1 will be heavily updated but S2 will mostly have few
> changes.
> I was thinking replication via the SQL server would be the best way to
> implement this but was wondering if it was possible.
> One of my concerns is that since the two servers are not connected all the
> time will they update correctly when they are connected.
> I am also concerned about how the system will handle records that are
> updated on both system and then merged.
> Also can the replication occur while the server is receiving new data?
> Any comments, suggestion, or links would be appreciated.
> Regards,
> John
>
|||Hi John,
From your descriptions, I understood that you would like to make
replication between two SQL Servers in Internet via modem. Have I
understood you? Correct me if I was wrong.
Based on my scope, first of all, you must select a way to setup replication
via Internet. Ways for users to connect to replicated data over the
Internet using Microsoft SQL Server 2000 include:
- Using Virtual Private Networks (VPNs), such as those based on the
Microsoft Windows NT? Server version 4.0 operating system, the Microsoft
Windows? 2000 Server operating system, or a third party provider.
- Integrating replication with Microsoft Proxy Server.
- Using TCP/IP and File Transfer Protocol (FTP) to transfer the initial
snapshot of data over the Internet.
See Topic "Web-Based Applications" in Books Online for more detailed
information about this and I would perfer using VPN. See the following
documents for how to create VPN on the different OS
How To Install and Configure a Virtual Private Network Server in Windows
Server 2003
http://support.microsoft.com/default...b;en-us;323441
Configure a Win2K VPN
http://msdn.microsoft.com/library/de...us/dnw2kmag00/
html/VPN.asp
How to Install Virtual Private Networking in Windows Me/98
http://support.microsoft.com/default...b;en-us;288779
Secondly, it was not necessary for you to connect to the Internet all the
time. You could schedule the synchronization at the same time per day with
a job, however, you will have to dial-up yourself that time before setup
the replication.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||The system will not be interfacing with the Internet at all. System 1 will
connect to system 2 using a 56K lease line or ISDN line. The only problem
is the connection is not permanent and must be initiated before update.
Regards,
John
""Michael Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:q0rLa$LvEHA.3696@.cpmsftngxa10.phx.gbl...
> Hi John,
> From your descriptions, I understood that you would like to make
> replication between two SQL Servers in Internet via modem. Have I
> understood you? Correct me if I was wrong.
> Based on my scope, first of all, you must select a way to setup
> replication
> via Internet. Ways for users to connect to replicated data over the
> Internet using Microsoft SQL Server 2000 include:
> - Using Virtual Private Networks (VPNs), such as those based on the
> Microsoft Windows NT? Server version 4.0 operating system, the Microsoft
> Windows? 2000 Server operating system, or a third party provider.
> - Integrating replication with Microsoft Proxy Server.
> - Using TCP/IP and File Transfer Protocol (FTP) to transfer the initial
> snapshot of data over the Internet.
> See Topic "Web-Based Applications" in Books Online for more detailed
> information about this and I would perfer using VPN. See the following
> documents for how to create VPN on the different OS
> How To Install and Configure a Virtual Private Network Server in Windows
> Server 2003
> http://support.microsoft.com/default...b;en-us;323441
> Configure a Win2K VPN
> http://msdn.microsoft.com/library/de...us/dnw2kmag00/
> html/VPN.asp
> How to Install Virtual Private Networking in Windows Me/98
> http://support.microsoft.com/default...b;en-us;288779
> Secondly, it was not necessary for you to connect to the Internet all the
> time. You could schedule the synchronization at the same time per day with
> a job, however, you will have to dial-up yourself that time before setup
> the replication.
> Thank you for your patience and corperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
|||Hi John,
Sorry for my misunderstanding.
If so, as MVP Dejan Sarka and I have said, it's OK for replication doing so
when the connection are not permanent. For example, you have scheduled the
run the SQL Agent at 6:00 PM everyday, you will have to dial-up before 6:00
PM everyday and make sure it was connect before SQL Agent doing this.
(Unfortuantely, based on my scope, I am afraid SQL Server do not have the
funcaitonality to dial-up automatically)
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Thanks for the response.
Regards,
John

Replication - will this work?

I have a system with two SQL 2K servers. The two servers are connected by
dial up 56K lines which will be used to update the system. The requirement
is that the first server S1 database match the second server S2 database on
a daily basis. S1 will be heavily updated but S2 will mostly have few
changes.
I was thinking replication via the SQL server would be the best way to
implement this but was wondering if it was possible.
One of my concerns is that since the two servers are not connected all the
time will they update correctly when they are connected.
I am also concerned about how the system will handle records that are
updated on both system and then merged.
Also can the replication occur while the server is receiving new data?
Any comments, suggestion, or links would be appreciated.
Regards,
JohnJohn,
Merge replication should do what you need, it is designed for occasionally
disconnected sites. Check it in Books Online whether this is what you need.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"John J. Hughes II" <no@.invalid.com> wrote in message
news:ueBIwtHvEHA.1296@.TK2MSFTNGP10.phx.gbl...
> I have a system with two SQL 2K servers. The two servers are connected by
> dial up 56K lines which will be used to update the system. The
requirement
> is that the first server S1 database match the second server S2 database
on
> a daily basis. S1 will be heavily updated but S2 will mostly have few
> changes.
> I was thinking replication via the SQL server would be the best way to
> implement this but was wondering if it was possible.
> One of my concerns is that since the two servers are not connected all the
> time will they update correctly when they are connected.
> I am also concerned about how the system will handle records that are
> updated on both system and then merged.
> Also can the replication occur while the server is receiving new data?
> Any comments, suggestion, or links would be appreciated.
> Regards,
> John
>|||Hi John,
From your descriptions, I understood that you would like to make
replication between two SQL Servers in Internet via modem. Have I
understood you? Correct me if I was wrong.
Based on my scope, first of all, you must select a way to setup replication
via Internet. Ways for users to connect to replicated data over the
Internet using Microsoft SQL Server 2000 include:
- Using Virtual Private Networks (VPNs), such as those based on the
Microsoft Windows NT? Server version 4.0 operating system, the Microsoft
Windows? 2000 Server operating system, or a third party provider.
- Integrating replication with Microsoft Proxy Server.
- Using TCP/IP and File Transfer Protocol (FTP) to transfer the initial
snapshot of data over the Internet.
See Topic "Web-Based Applications" in Books Online for more detailed
information about this and I would perfer using VPN. See the following
documents for how to create VPN on the different OS
How To Install and Configure a Virtual Private Network Server in Windows
Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323441
Configure a Win2K VPN
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnw2kmag00/
html/VPN.asp
How to Install Virtual Private Networking in Windows Me/98
http://support.microsoft.com/default.aspx?scid=kb;en-us;288779
Secondly, it was not necessary for you to connect to the Internet all the
time. You could schedule the synchronization at the same time per day with
a job, however, you will have to dial-up yourself that time before setup
the replication.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||The system will not be interfacing with the Internet at all. System 1 will
connect to system 2 using a 56K lease line or ISDN line. The only problem
is the connection is not permanent and must be initiated before update.
Regards,
John
""Michael Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:q0rLa$LvEHA.3696@.cpmsftngxa10.phx.gbl...
> Hi John,
> From your descriptions, I understood that you would like to make
> replication between two SQL Servers in Internet via modem. Have I
> understood you? Correct me if I was wrong.
> Based on my scope, first of all, you must select a way to setup
> replication
> via Internet. Ways for users to connect to replicated data over the
> Internet using Microsoft SQL Server 2000 include:
> - Using Virtual Private Networks (VPNs), such as those based on the
> Microsoft Windows NT? Server version 4.0 operating system, the Microsoft
> Windows? 2000 Server operating system, or a third party provider.
> - Integrating replication with Microsoft Proxy Server.
> - Using TCP/IP and File Transfer Protocol (FTP) to transfer the initial
> snapshot of data over the Internet.
> See Topic "Web-Based Applications" in Books Online for more detailed
> information about this and I would perfer using VPN. See the following
> documents for how to create VPN on the different OS
> How To Install and Configure a Virtual Private Network Server in Windows
> Server 2003
> http://support.microsoft.com/default.aspx?scid=kb;en-us;323441
> Configure a Win2K VPN
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnw2kmag00/
> html/VPN.asp
> How to Install Virtual Private Networking in Windows Me/98
> http://support.microsoft.com/default.aspx?scid=kb;en-us;288779
> Secondly, it was not necessary for you to connect to the Internet all the
> time. You could schedule the synchronization at the same time per day with
> a job, however, you will have to dial-up yourself that time before setup
> the replication.
> Thank you for your patience and corperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>|||Hi John,
Sorry for my misunderstanding.
If so, as MVP Dejan Sarka and I have said, it's OK for replication doing so
when the connection are not permanent. For example, you have scheduled the
run the SQL Agent at 6:00 PM everyday, you will have to dial-up before 6:00
PM everyday and make sure it was connect before SQL Agent doing this.
(Unfortuantely, based on my scope, I am afraid SQL Server do not have the
funcaitonality to dial-up automatically)
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thanks for the response.
Regards,
John

Replication - will this work?

I have a system with two SQL 2K servers. The two servers are connected by
dial up 56K lines which will be used to update the system. The requirement
is that the first server S1 database match the second server S2 database on
a daily basis. S1 will be heavily updated but S2 will mostly have few
changes.
I was thinking replication via the SQL server would be the best way to
implement this but was wondering if it was possible.
One of my concerns is that since the two servers are not connected all the
time will they update correctly when they are connected.
I am also concerned about how the system will handle records that are
updated on both system and then merged.
Also can the replication occur while the server is receiving new data?
Any comments, suggestion, or links would be appreciated.
Regards,
JohnJohn,
Merge replication should do what you need, it is designed for occasionally
disconnected sites. Check it in Books Online whether this is what you need.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"John J. Hughes II" <no@.invalid.com> wrote in message
news:ueBIwtHvEHA.1296@.TK2MSFTNGP10.phx.gbl...
> I have a system with two SQL 2K servers. The two servers are connected by
> dial up 56K lines which will be used to update the system. The
requirement
> is that the first server S1 database match the second server S2 database
on
> a daily basis. S1 will be heavily updated but S2 will mostly have few
> changes.
> I was thinking replication via the SQL server would be the best way to
> implement this but was wondering if it was possible.
> One of my concerns is that since the two servers are not connected all the
> time will they update correctly when they are connected.
> I am also concerned about how the system will handle records that are
> updated on both system and then merged.
> Also can the replication occur while the server is receiving new data?
> Any comments, suggestion, or links would be appreciated.
> Regards,
> John
>|||Hi John,
From your descriptions, I understood that you would like to make
replication between two SQL Servers in Internet via modem. Have I
understood you? Correct me if I was wrong.
Based on my scope, first of all, you must select a way to setup replication
via Internet. Ways for users to connect to replicated data over the
Internet using Microsoft SQL Server 2000 include:
- Using Virtual Private Networks (VPNs), such as those based on the
Microsoft Windows NT? Server version 4.0 operating system, the Microsoft
Windows? 2000 Server operating system, or a third party provider.
- Integrating replication with Microsoft Proxy Server.
- Using TCP/IP and File Transfer Protocol (FTP) to transfer the initial
snapshot of data over the Internet.
See Topic "Web-Based Applications" in Books Online for more detailed
information about this and I would perfer using VPN. See the following
documents for how to create VPN on the different OS
How To Install and Configure a Virtual Private Network Server in Windows
Server 2003
http://support.microsoft.com/defaul...kb;en-us;323441
Configure a Win2K VPN
http://msdn.microsoft.com/library/d...-us/dnw2kmag00/
html/VPN.asp
How to Install Virtual Private Networking in Windows Me/98
http://support.microsoft.com/defaul...kb;en-us;288779
Secondly, it was not necessary for you to connect to the Internet all the
time. You could schedule the synchronization at the same time per day with
a job, however, you will have to dial-up yourself that time before setup
the replication.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||The system will not be interfacing with the Internet at all. System 1 will
connect to system 2 using a 56K lease line or ISDN line. The only problem
is the connection is not permanent and must be initiated before update.
Regards,
John
""Michael Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messag
e
news:q0rLa$LvEHA.3696@.cpmsftngxa10.phx.gbl...
> Hi John,
> From your descriptions, I understood that you would like to make
> replication between two SQL Servers in Internet via modem. Have I
> understood you? Correct me if I was wrong.
> Based on my scope, first of all, you must select a way to setup
> replication
> via Internet. Ways for users to connect to replicated data over the
> Internet using Microsoft SQL Server 2000 include:
> - Using Virtual Private Networks (VPNs), such as those based on the
> Microsoft Windows NT? Server version 4.0 operating system, the Microsoft
> Windows? 2000 Server operating system, or a third party provider.
> - Integrating replication with Microsoft Proxy Server.
> - Using TCP/IP and File Transfer Protocol (FTP) to transfer the initial
> snapshot of data over the Internet.
> See Topic "Web-Based Applications" in Books Online for more detailed
> information about this and I would perfer using VPN. See the following
> documents for how to create VPN on the different OS
> How To Install and Configure a Virtual Private Network Server in Windows
> Server 2003
> http://support.microsoft.com/defaul...kb;en-us;323441
> Configure a Win2K VPN
> http://msdn.microsoft.com/library/d...kb;en-us;288779
> Secondly, it was not necessary for you to connect to the Internet all the
> time. You could schedule the synchronization at the same time per day with
> a job, however, you will have to dial-up yourself that time before setup
> the replication.
> Thank you for your patience and corperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Michael Cheng
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---
> Get Secure! - http://www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>|||Hi John,
Sorry for my misunderstanding.
If so, as MVP Dejan Sarka and I have said, it's OK for replication doing so
when the connection are not permanent. For example, you have scheduled the
run the SQL Agent at 6:00 PM everyday, you will have to dial-up before 6:00
PM everyday and make sure it was connect before SQL Agent doing this.
(Unfortuantely, based on my scope, I am afraid SQL Server do not have the
funcaitonality to dial-up automatically)
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thanks for the response.
Regards,
John

Replication - distribution agents?

When distribution is scheduled to run at specific times for specific user, but that user is not connected to the server. Distribution tries to find that subscription, the error comes back:

The step was retried the requested number of times(10) without succeeding.

Where/how can I change the requested number to try two or three times.

My problem is that it takes 10-15 minutes for those re-trys and which sometimes causes overlap with the next subscription coming in.Check sp_update_jobstep in BOL, look for @.retry_attempts and @.retry_interval
The best way would be to use a PULL subscription at the subscriber instead of PUSH at the publisher.

Originally posted by cruzin
When distribution is scheduled to run at specific times for specific user, but that user is not connected to the server. Distribution tries to find that subscription, the error comes back:

The step was retried the requested number of times(10) without succeeding.

Where/how can I change the requested number to try two or three times.

My problem is that it takes 10-15 minutes for those re-trys and which sometimes causes overlap with the next subscription coming in.|||You can also identify the job in Enterprise Manager (Management->SQL Server Agent-> Jobs) then find the step and change the retry attempts there.

Originally posted by dbadelphes
Check sp_update_jobstep in BOL, look for @.retry_attempts and @.retry_interval
The best way would be to use a PULL subscription at the subscriber instead of PUSH at the publisher.

Replication

We have two systems one that has a domain setup and the other is a workgroup. We have them connected over a non-trusted internet connection. We are using SQL Server 2005 Enterprise version, for Peer-to-Peer transactional replication, the server that hasa domain, is called EXT-FRMAC1 and the other one is FRMAC_DC. FRMAC_DC can subscribe to EXT-FRMAC1's publication, but EXT-FRMAC1 can't subscribe to FRMAC_DC, and the error that we get on FRMAC_DC, is that FRMAC_DC\admin - username or password does not exist. admin exists on FRMAC_DC, I am not sure if we should try and put it on a domain or not.

Thanks.

Have you tried to setup with a SQL server account instead of Windows account?

Gary

Replicating MSDE & SQL2000

Hi All,
What is the best way to merge/replicate SQL2000 & MSDE? We have an app that
laptop users will be running locally when not connected to the network.
When they come into the office we want their local DB on their laptop which
would be MSDE to connect to the SQL2000 Server and the 2 databases to update
each other.
Any references/websites addressing this would be great.
Thanks
Lee
I think you will want to use merge replication. It was designed for just
this kind of situation. Replication is a rather broad topic. The BOL has
lots of information. I would recommend setting up a couple of test databases
and experimenting with replication, just to get familiar with it.
Jim
"Lee Trotter" <latrotter@.@.@.sympatico.ca> wrote in message
news:epJHkFLVEHA.1292@.TK2MSFTNGP10.phx.gbl...
> Hi All,
> What is the best way to merge/replicate SQL2000 & MSDE? We have an app
that
> laptop users will be running locally when not connected to the network.
> When they come into the office we want their local DB on their laptop
which
> would be MSDE to connect to the SQL2000 Server and the 2 databases to
update
> each other.
> Any references/websites addressing this would be great.
> Thanks
> Lee
>