Friday, March 23, 2012
Merge Replication SQL Server 2005 and SQL Express
SQL Server 2005 and potentially a hundred or so instances of SQL Express
subscribers. Our business model is such that the SQL Express users will not
be online all the time and when they are the merge replication will take
place over an HTTPS connection, which I understand is supported. Since data
changes can occur on either or both ends does the fact that SQL Express is
only a subscriber mean that the changes made on that end won't be propogated
back to the SQL Server unless SQL Server requests them? Is it best to
schedule the replications? Is HTTPS or FTP the better mechanism for
transport?
Where can I find some examples or tutorials of setting up replication
between SQL Server 2005 and SQL Express?
Thanks!
RSH
I also noticed that when performing a DDL change, I could do it at the
Publisher level and the change propogated to the subscribers...IF and only
IF when I added columns I didn't insert them BEFORE the RowGuid. Is this a
bug or is this correct behaviour?
"RSH" <way_beyond_oops@.yahoo.com> wrote in message
news:Of%23IsMD9FHA.4036@.TK2MSFTNGP11.phx.gbl...
> We are going to be implementing merge replication between a main instance
> of SQL Server 2005 and potentially a hundred or so instances of SQL
> Express subscribers. Our business model is such that the SQL Express
> users will not be online all the time and when they are the merge
> replication will take place over an HTTPS connection, which I understand
> is supported. Since data changes can occur on either or both ends does
> the fact that SQL Express is only a subscriber mean that the changes made
> on that end won't be propogated back to the SQL Server unless SQL Server
> requests them? Is it best to schedule the replications? Is HTTPS or FTP
> the better mechanism for transport?
> Where can I find some examples or tutorials of setting up replication
> between SQL Server 2005 and SQL Express?
> Thanks!
> RSH
>
|||Data flow is in each direction even though SQL Express is limited to being a
subscriber. FTP is used for initialization while the HTTPS transport is for
the subsequent synchronizations. The info in BOL is pretty comprehensive for
this new functionality and AFAIK there are no articles outside of BOL on the
setup.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Can you run sp_helpmergepublication and let us know the value of
replicate_ddl.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I simply get "
Command(s) completed successfully."
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ebzCtSD9FHA.808@.TK2MSFTNGP09.phx.gbl...
> Can you run sp_helpmergepublication and let us know the value of
> replicate_ddl.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||This needs to be executed at the Publisher on the publication database.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||replicate_ddl = 1
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ebzCtSD9FHA.808@.TK2MSFTNGP09.phx.gbl...
> Can you run sp_helpmergepublication and let us know the value of
> replicate_ddl.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
Saturday, February 25, 2012
Merge replication between two instances.
instances of SQL Server in the same computer?
yes, I do it all the time.
"Jose M. Marn" <jm_marintl@.eresmas.com> wrote in message
news:eWIOshhYEHA.2816@.TK2MSFTNGP11.phx.gbl...
> Does anybody know if it is possible to make a merge replication between
two
> instances of SQL Server in the same computer?
>
Merge Replication between MSDE doesn't work!
Hello!
I have a problem with creating Merge replication between two instances of MSDE 2000. In the article http://support.microsoft.com/kb/324992/, published by Microsoft, described, that it is possible.
I am creating Merge Publication at MSDE 2000, with Distributor and Publisher configured at same machine, with options "Allow Pull Subscriptions" and "Allow Anonymous Subscriptions". There is no problem with creating of Publication. Even snapshot generation finishes successfully. Also I create a login with SQL Server Authentication and "System Administrators" database role at the publisher in order to connect to it from Subscriber.
The problem occurs, when creating anonymous pull subscription to this publication at another instance of MSDE. During initial synchronization an error occurs:
The process could not connect to Distributor '<publisher_server_name>'. Login failed for user '<login_created_at_publisher>'. Reason: Not associated with a trusted SQL Server connection. The step failed.
Although I didn't use Windows Authentication at all, so Subscriber doesn't need to connect to Distributor using trusted SQL Server connection.
What is a problem and how can I workaround?
Note: The same works correctly, if MS SQL Server used as a Publisher instead of MSDE.
Please, help!
I can provide publication and subscription creation scripts, if required.
Guys, don't care anymore: I found the reason!!!
Probably, the problem was in using an old version of MSDE, and installing MSDE with SP4 solved it!
However, there are still some problems with connecting to MSDE from a remote workstation via named pipes, but I think I can research it independently.
Thanks for consideration!
Merge Replication between MSDE doesn't work!
Hello!
I have a problem with creating Merge replication between two instances of MSDE 2000. In the article http://support.microsoft.com/kb/324992/, published by Microsoft, described, that it is possible.
I am creating Merge Publication at MSDE 2000, with Distributor and Publisher configured at same machine, with options "Allow Pull Subscriptions" and "Allow Anonymous Subscriptions". There is no problem with creating of Publication. Even snapshot generation finishes successfully. Also I create a login with SQL Server Authentication and "System Administrators" database role at the publisher in order to connect to it from Subscriber.
The problem occurs, when creating anonymous pull subscription to this publication at another instance of MSDE. During initial synchronization an error occurs:
The process could not connect to Distributor '<publisher_server_name>'. Login failed for user '<login_created_at_publisher>'. Reason: Not associated with a trusted SQL Server connection. The step failed.
Although I didn't use Windows Authentication at all, so Subscriber doesn't need to connect to Distributor using trusted SQL Server connection.
What is a problem and how can I workaround?
Note: The same works correctly, if MS SQL Server used as a Publisher instead of MSDE.
Please, help!
I can provide publication and subscription creation scripts, if required.
Guys, don't care anymore: I found the reason!!!
Probably, the problem was in using an old version of MSDE, and installing MSDE with SP4 solved it!
However, there are still some problems with connecting to MSDE from a remote workstation via named pipes, but I think I can research it independently.
Thanks for consideration!