Good morning,
I am attempting to set up merge replication between a SQL Server on SBS2003
box (publisher and distributor) and a SQL Server 2000 box (subscriber) in a
different state (hosted, connect via IP addresses).
I can push the publication to the subscriber, but the synch process fails
with error 14010 (I think..not in front of right now).
This is my first attempt at replication...any help is appreciated
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||Kevin,
are you using an IP address - it'll need to be an alias instead. Have a look
at this article to see if you have missed anything out:
http://support.microsoft.com/?id=321822
HTH,
Paul Ibison
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||My bad...I have set up the alias through the Client Network Utility on the
Publisher, using the correct name of the server as the alias name. Did same
at the Subscriber to connect to the Publisher...
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> Kevin,
> are you using an IP address - it'll need to be an alias instead. Have a
look
> at this article to see if you have missed anything out:
> http://support.microsoft.com/?id=321822
> HTH,
> Paul Ibison
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||make sure you download the snapshot using FTP and use anonymous pull
subscribers.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
> My bad...I have set up the alias through the Client Network Utility on the
> Publisher, using the correct name of the server as the alias name. Did
same
> at the Subscriber to connect to the Publisher...
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
> news:%23M5rAAfXEHA.3988@.tk2msftngp13.phx.gbl...
> look
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||OK...so a push to the subscriber does not work? Is that only for
local/Lan/trusted setups?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> make sure you download the snapshot using FTP and use anonymous pull
> subscribers.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
> news:O7uf3GfXEHA.1036@.TK2MSFTNGP10.phx.gbl...
the[vbcol=seagreen]
> same
a
>
|||Not really. You can push or pull within a LAN, locally, or within a trusted
network or across a WAN, Internet, etc.
The decision to use push or pull depends on many factors
1) pull performance is better, but you have no central point of
administration
2) It is a security risk to open the ports necessary to push over the
internet.
3) You can't do a push using FTP.
4) pull is better when your subscribers are occasionally connected, push is
better when they are always connected.
In general when you hear the word internet - think pull.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:OEs0JSgXEHA.1292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> OK...so a push to the subscriber does not work? Is that only for
> local/Lan/trusted setups?
> --
> Kevin Hill
> President
> 3NF Consulting
> www.3nf-inc.com/NewsGroups.htm
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:%236%23vp4fXEHA.1292@.TK2MSFTNGP11.phx.gbl...
> the
Did[vbcol=seagreen]
DBAs.[vbcol=seagreen]
Have
> a
>
Showing posts with label box. Show all posts
Showing posts with label box. Show all posts
Monday, March 19, 2012
Monday, March 12, 2012
Merge replication missing transactions
I have 2 servers, one running SQL 2000 and one running SQL 7. On the 2000 box I have 2 databases which are replicating between each other fine using Transactional replication. (One way replication only)
I also wish to use replication to keep a database on the SQL 7 box up to date. (Again the dataflow is ALL one way between the 3 databases)
I have set up Merge replication between these two due to transactional replication not working correctly between the different versions of SQL Server. (I belive this is due to SQL 7 using a date stamp as the unique ID on the table columns and 2000 using a GUID.)
Now whenever I issue an insert/update/delete to the first database in the chain, transactional replication updates the 2nd ok, but merge replication then fails to update the database on the 3rd server.
If I issue an insert/update/delete to the 2nd database in the chain the change is replicated correctly.
Any ideas?...Upgrade SQL2k to SP3. Microsoft have updated this but didn't publicise it at all!
If anyone has any problems with this email me at my username @.hotmail.com.
Cheers,|||Upgrade SQL2k to SP3. Microsoft have updated this but didn't publicise it at all!
If anyone has any problems with this email me at my username @.hotmail.com.
Cheers,
I also wish to use replication to keep a database on the SQL 7 box up to date. (Again the dataflow is ALL one way between the 3 databases)
I have set up Merge replication between these two due to transactional replication not working correctly between the different versions of SQL Server. (I belive this is due to SQL 7 using a date stamp as the unique ID on the table columns and 2000 using a GUID.)
Now whenever I issue an insert/update/delete to the first database in the chain, transactional replication updates the 2nd ok, but merge replication then fails to update the database on the 3rd server.
If I issue an insert/update/delete to the 2nd database in the chain the change is replicated correctly.
Any ideas?...Upgrade SQL2k to SP3. Microsoft have updated this but didn't publicise it at all!
If anyone has any problems with this email me at my username @.hotmail.com.
Cheers,|||Upgrade SQL2k to SP3. Microsoft have updated this but didn't publicise it at all!
If anyone has any problems with this email me at my username @.hotmail.com.
Cheers,
Merge Replication Issue. Update not happening
Hi,
We have set up merge replication between a few boxes. I make changes on one
box, replicate, and check the tables on the other box. The inserts are being
replicated, and some updates.
It appears that the updates made out of a stored proc are not being
replicated. I can manually update the table, and it will be replicated. But
when updated from the stored proc, it is not coming accrossed.
Any ideas?
Steve
More info.
sp3, no conflicts reported, after further testing, it seems one column on
one table never gets updated. Other columns that didn't, did at other times.
It is of type bit. I can manually update it and replicate, but can't have
the stored procedure update it and replicate.
"SteveInBeloit" wrote:
> Hi,
> We have set up merge replication between a few boxes. I make changes on one
> box, replicate, and check the tables on the other box. The inserts are being
> replicated, and some updates.
> It appears that the updates made out of a stored proc are not being
> replicated. I can manually update the table, and it will be replicated. But
> when updated from the stored proc, it is not coming accrossed.
> Any ideas?
> Steve
>
|||Just went to sp4, that did not help. When I do a "validate" after the
replicate, the checksum for that table fails.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> More info.
> sp3, no conflicts reported, after further testing, it seems one column on
> one table never gets updated. Other columns that didn't, did at other times.
> It is of type bit. I can manually update it and replicate, but can't have
> the stored procedure update it and replicate.
>
> "SteveInBeloit" wrote:
|||More info - it is a Pull initiated at the subscriber. If I run the same
application on the Publisher, and make the updates, then replicate, the
change gets to the subscriber, just not the other way around.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> Just went to sp4, that did not help. When I do a "validate" after the
> replicate, the checksum for that table fails.
> "SteveInBeloit" wrote:
|||Solved:
It was actually a delete and an insert, not an update. A record had been
written to a ##TempTable. Processing was done on that record. Then the GUID
key of that row was used to delete the row out of the real table, then and
INSERT from the temp to the real table to put it back. On that insert, I
used the same GUID key instead of letting the table NEWID get a new one. It
confused replication, having known there was a DELETE and and INSERT, but the
GUIDs the same.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> More info - it is a Pull initiated at the subscriber. If I run the same
> application on the Publisher, and make the updates, then replicate, the
> change gets to the subscriber, just not the other way around.
> "SteveInBeloit" wrote:
We have set up merge replication between a few boxes. I make changes on one
box, replicate, and check the tables on the other box. The inserts are being
replicated, and some updates.
It appears that the updates made out of a stored proc are not being
replicated. I can manually update the table, and it will be replicated. But
when updated from the stored proc, it is not coming accrossed.
Any ideas?
Steve
More info.
sp3, no conflicts reported, after further testing, it seems one column on
one table never gets updated. Other columns that didn't, did at other times.
It is of type bit. I can manually update it and replicate, but can't have
the stored procedure update it and replicate.
"SteveInBeloit" wrote:
> Hi,
> We have set up merge replication between a few boxes. I make changes on one
> box, replicate, and check the tables on the other box. The inserts are being
> replicated, and some updates.
> It appears that the updates made out of a stored proc are not being
> replicated. I can manually update the table, and it will be replicated. But
> when updated from the stored proc, it is not coming accrossed.
> Any ideas?
> Steve
>
|||Just went to sp4, that did not help. When I do a "validate" after the
replicate, the checksum for that table fails.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> More info.
> sp3, no conflicts reported, after further testing, it seems one column on
> one table never gets updated. Other columns that didn't, did at other times.
> It is of type bit. I can manually update it and replicate, but can't have
> the stored procedure update it and replicate.
>
> "SteveInBeloit" wrote:
|||More info - it is a Pull initiated at the subscriber. If I run the same
application on the Publisher, and make the updates, then replicate, the
change gets to the subscriber, just not the other way around.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> Just went to sp4, that did not help. When I do a "validate" after the
> replicate, the checksum for that table fails.
> "SteveInBeloit" wrote:
|||Solved:
It was actually a delete and an insert, not an update. A record had been
written to a ##TempTable. Processing was done on that record. Then the GUID
key of that row was used to delete the row out of the real table, then and
INSERT from the temp to the real table to put it back. On that insert, I
used the same GUID key instead of letting the table NEWID get a new one. It
confused replication, having known there was a DELETE and and INSERT, but the
GUIDs the same.
"SteveInBeloit" wrote:
[vbcol=seagreen]
> More info - it is a Pull initiated at the subscriber. If I run the same
> application on the Publisher, and make the updates, then replicate, the
> change gets to the subscriber, just not the other way around.
> "SteveInBeloit" wrote:
Friday, March 9, 2012
merge replication error 208
Hi All,
I have an SQL server 2000 as a distributor & Publisher, in other box SQL
Server 2000 as a subscriber.
Also I have one replication successful running and when I try to create a
new Publication I got the same error for many tables.
SQL could not initialize an article base on table 'table name'
Error 208. Invalid object name 'sysmergeextendedarticleview'
What is the problem? How can I fixed?
Tks in advance
Johnny
Can you please provide more detail about your setup:
1. What type of publication is setup? Is it working correctly?
2. What commands are you using to add publication?
3. If you provide the script used for setting up replication - it will be
easier to understand your issue.
thanks - deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"JFB" <jfb@.newSQL.com> wrote in message
news:ORgKceb%23EHA.4028@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> I have an SQL server 2000 as a distributor & Publisher, in other box SQL
> Server 2000 as a subscriber.
> Also I have one replication successful running and when I try to create a
> new Publication I got the same error for many tables.
> SQL could not initialize an article base on table 'table name'
> Error 208. Invalid object name 'sysmergeextendedarticleview'
> What is the problem? How can I fixed?
> Tks in advance
> Johnny
>
I have an SQL server 2000 as a distributor & Publisher, in other box SQL
Server 2000 as a subscriber.
Also I have one replication successful running and when I try to create a
new Publication I got the same error for many tables.
SQL could not initialize an article base on table 'table name'
Error 208. Invalid object name 'sysmergeextendedarticleview'
What is the problem? How can I fixed?
Tks in advance
Johnny
Can you please provide more detail about your setup:
1. What type of publication is setup? Is it working correctly?
2. What commands are you using to add publication?
3. If you provide the script used for setting up replication - it will be
easier to understand your issue.
thanks - deepak
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"JFB" <jfb@.newSQL.com> wrote in message
news:ORgKceb%23EHA.4028@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> I have an SQL server 2000 as a distributor & Publisher, in other box SQL
> Server 2000 as a subscriber.
> Also I have one replication successful running and when I try to create a
> new Publication I got the same error for many tables.
> SQL could not initialize an article base on table 'table name'
> Error 208. Invalid object name 'sysmergeextendedarticleview'
> What is the problem? How can I fixed?
> Tks in advance
> Johnny
>
Wednesday, March 7, 2012
Merge Replication Error
Hello,
I have a publiction on my development box using SQL Server 2005 developer
edition. I created a subscription for my test box, sitting next to me,
intialized and synchronized with the subscriber. I also have SQL Server
Express installed on my development box. I created a subscription for this
server and tried to initialize and sychronize with that subscriber. However,
the subscription never appears in that servers Local Subscriptions list.
The SQL Server Agent is running under a domain account that we use for
replication and this account has the neccessary permissions on each
subcribers machines including my dev box. However, I get the error:
The job failed. Unable to determine if the owner (domain\username) of job
MachineName\SQL2005-Weed-WeedMerge-MachineName\SQLEXPRESS-14 has server
access (reason: Could not obtain information about Windows NT group/user
'domain\username', error code 0xea. [SQLSTATE 42000] (Error 15404) The
statement has been terminated. [SQLSTATE 01000] (Error 3621)).
When I view the job history.
Can anyone help me with this?
S
Just changing the job owner to sa should do it.
Cheers,
Paul Ibison
|||You might also want to consider using a SQL account for the merge agent.
relevantNoise - dedicated to mining blogs for business intelligence.
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
"SAL" <SAL_@.NoNo.com> wrote in message
news:OunlT8o3HHA.5184@.TK2MSFTNGP02.phx.gbl...
> Hello,
> I have a publiction on my development box using SQL Server 2005 developer
> edition. I created a subscription for my test box, sitting next to me,
> intialized and synchronized with the subscriber. I also have SQL Server
> Express installed on my development box. I created a subscription for this
> server and tried to initialize and sychronize with that subscriber.
> However, the subscription never appears in that servers Local
> Subscriptions list.
> The SQL Server Agent is running under a domain account that we use for
> replication and this account has the neccessary permissions on each
> subcribers machines including my dev box. However, I get the error:
> The job failed. Unable to determine if the owner (domain\username) of job
> MachineName\SQL2005-Weed-WeedMerge-MachineName\SQLEXPRESS-14 has server
> access (reason: Could not obtain information about Windows NT group/user
> 'domain\username', error code 0xea. [SQLSTATE 42000] (Error 15404) The
> statement has been terminated. [SQLSTATE 01000] (Error 3621)).
> When I view the job history.
> Can anyone help me with this?
> S
>
|||Hi Paul,
I did try that but what finally worked was changing the account that SQL
Server runs under to the account that it couldn't determine if it had access
rights.
So, event though the owner of the job was the domain replication account,
SQL Server Express was running under a different account and the job was
actually running under my acccount. I change SQL Server Expresses log on
account to me and it started working. This only seemed to be a problem on my
dev server for some reason.
Thanks again.
S
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:75E0428A-BF72-4E1E-B428-76743E99AEA5@.microsoft.com...
> Just changing the job owner to sa should do it.
> Cheers,
> Paul Ibison
>
I have a publiction on my development box using SQL Server 2005 developer
edition. I created a subscription for my test box, sitting next to me,
intialized and synchronized with the subscriber. I also have SQL Server
Express installed on my development box. I created a subscription for this
server and tried to initialize and sychronize with that subscriber. However,
the subscription never appears in that servers Local Subscriptions list.
The SQL Server Agent is running under a domain account that we use for
replication and this account has the neccessary permissions on each
subcribers machines including my dev box. However, I get the error:
The job failed. Unable to determine if the owner (domain\username) of job
MachineName\SQL2005-Weed-WeedMerge-MachineName\SQLEXPRESS-14 has server
access (reason: Could not obtain information about Windows NT group/user
'domain\username', error code 0xea. [SQLSTATE 42000] (Error 15404) The
statement has been terminated. [SQLSTATE 01000] (Error 3621)).
When I view the job history.
Can anyone help me with this?
S
Just changing the job owner to sa should do it.
Cheers,
Paul Ibison
|||You might also want to consider using a SQL account for the merge agent.
relevantNoise - dedicated to mining blogs for business intelligence.
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
"SAL" <SAL_@.NoNo.com> wrote in message
news:OunlT8o3HHA.5184@.TK2MSFTNGP02.phx.gbl...
> Hello,
> I have a publiction on my development box using SQL Server 2005 developer
> edition. I created a subscription for my test box, sitting next to me,
> intialized and synchronized with the subscriber. I also have SQL Server
> Express installed on my development box. I created a subscription for this
> server and tried to initialize and sychronize with that subscriber.
> However, the subscription never appears in that servers Local
> Subscriptions list.
> The SQL Server Agent is running under a domain account that we use for
> replication and this account has the neccessary permissions on each
> subcribers machines including my dev box. However, I get the error:
> The job failed. Unable to determine if the owner (domain\username) of job
> MachineName\SQL2005-Weed-WeedMerge-MachineName\SQLEXPRESS-14 has server
> access (reason: Could not obtain information about Windows NT group/user
> 'domain\username', error code 0xea. [SQLSTATE 42000] (Error 15404) The
> statement has been terminated. [SQLSTATE 01000] (Error 3621)).
> When I view the job history.
> Can anyone help me with this?
> S
>
|||Hi Paul,
I did try that but what finally worked was changing the account that SQL
Server runs under to the account that it couldn't determine if it had access
rights.
So, event though the owner of the job was the domain replication account,
SQL Server Express was running under a different account and the job was
actually running under my acccount. I change SQL Server Expresses log on
account to me and it started working. This only seemed to be a problem on my
dev server for some reason.
Thanks again.
S
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:75E0428A-BF72-4E1E-B428-76743E99AEA5@.microsoft.com...
> Just changing the job owner to sa should do it.
> Cheers,
> Paul Ibison
>
Saturday, February 25, 2012
merge replication compatibility issue
All,
I have a SQL2005 server that is running merge replication against SQL2000
boxes. One of my SQL2000 box needed to be replaced due to disk issues. I
scripted out my Subscription from my 2005 box and tried to reapply it after I
rebuilt my new 2000 box. When I run the script I get an error saying:
"Publication 'PubName' cannot be added to database 'DBNAme', because a
publication with a higher compatibility level already exists. All merge
publications in a database must have the same compatibiliy level."
I am in the process of upgrading all my 2000 boxes, but this one, since i
was having issues I wanted to get it back to its original state before
upgrading it.
Right now there is a mix of replications running pointing to a few SQl2000
and Some SQL2005.
Is there a way to get around this before upgrading my new box to 2005?
TIA,
John
Similar, but what I had to do was to change the compatibilty level of all my
subscriptions to 2005 and I was able to add this new one back in.
Thanks for the response.
"Paul Ibison" wrote:
> Is this related to your issue:
> [url]http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.replica tion&tid=4e5d642b-a4c0-4574-8bae-98fcc88e19b8&p=1[/url]
> IE I'm wondering if you have a republishing setup.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
|||John,
I had very similar situation just the other day, where somebody deleted
publication on SQL2000's level while
there were some pubs already created in 2005's level and I needed to
recreate the publication.
I somehow managed to fix it, but I'm afraid I might have lost some
unsynchronized data in the process - I'm not sure it was the best way to do
it. Could you post step by step description how did you handle it?
thanks,
r
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:C284873D-DD99-45A5-A191-047EE33E004E@.microsoft.com...[vbcol=seagreen]
> Similar, but what I had to do was to change the compatibilty level of all
> my
> subscriptions to 2005 and I was able to add this new one back in.
> Thanks for the response.
> "Paul Ibison" wrote:
|||I scrpited out my replication as a delete and create.
I ran the delete with no issues, but when I tried to run the create that's
when I fell into the compatibilty issue.
i changed all the SQL 200 compatibity levels to 2005 and changed my script
from 80rtm to 90rtm on the create statement of the script SQl generated.
I reran the create and it created with no issues. I started my agent and
synced my data since I only care about what happens here in my main office
anything changed at my branch got overwritten if there were any changes at
both places.
Is that the same way you did yours? maybe you had a better solution, mine
seemed to work for me but I am always looking for better and different
solutions.
"Rafael Lenartowicz" wrote:
> John,
> I had very similar situation just the other day, where somebody deleted
> publication on SQL2000's level while
> there were some pubs already created in 2005's level and I needed to
> recreate the publication.
> I somehow managed to fix it, but I'm afraid I might have lost some
> unsynchronized data in the process - I'm not sure it was the best way to do
> it. Could you post step by step description how did you handle it?
> thanks,
> r
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:C284873D-DD99-45A5-A191-047EE33E004E@.microsoft.com...
>
>
|||how did you manage to change the compatibility level? using
sp_changemergepublication ?
I wasn't able to do it, it was complaining something about the incompatible
snapshot...
besides - in my setup the data from the remote location IS the vital data -
they submiting their
daily revenue reports to the central office reporting server, I can't have
anything overwritten or lost.
thanks
r
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:EE97BCC9-6445-44F4-BF33-D115DDD98B43@.microsoft.com...[vbcol=seagreen]
>I scrpited out my replication as a delete and create.
> I ran the delete with no issues, but when I tried to run the create that's
> when I fell into the compatibilty issue.
> i changed all the SQL 200 compatibity levels to 2005 and changed my script
> from 80rtm to 90rtm on the create statement of the script SQl generated.
> I reran the create and it created with no issues. I started my agent and
> synced my data since I only care about what happens here in my main office
> anything changed at my branch got overwritten if there were any changes at
> both places.
> Is that the same way you did yours? maybe you had a better solution, mine
> seemed to work for me but I am always looking for better and different
> solutions.
> "Rafael Lenartowicz" wrote:
I have a SQL2005 server that is running merge replication against SQL2000
boxes. One of my SQL2000 box needed to be replaced due to disk issues. I
scripted out my Subscription from my 2005 box and tried to reapply it after I
rebuilt my new 2000 box. When I run the script I get an error saying:
"Publication 'PubName' cannot be added to database 'DBNAme', because a
publication with a higher compatibility level already exists. All merge
publications in a database must have the same compatibiliy level."
I am in the process of upgrading all my 2000 boxes, but this one, since i
was having issues I wanted to get it back to its original state before
upgrading it.
Right now there is a mix of replications running pointing to a few SQl2000
and Some SQL2005.
Is there a way to get around this before upgrading my new box to 2005?
TIA,
John
Similar, but what I had to do was to change the compatibilty level of all my
subscriptions to 2005 and I was able to add this new one back in.
Thanks for the response.
"Paul Ibison" wrote:
> Is this related to your issue:
> [url]http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.replica tion&tid=4e5d642b-a4c0-4574-8bae-98fcc88e19b8&p=1[/url]
> IE I'm wondering if you have a republishing setup.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>
|||John,
I had very similar situation just the other day, where somebody deleted
publication on SQL2000's level while
there were some pubs already created in 2005's level and I needed to
recreate the publication.
I somehow managed to fix it, but I'm afraid I might have lost some
unsynchronized data in the process - I'm not sure it was the best way to do
it. Could you post step by step description how did you handle it?
thanks,
r
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:C284873D-DD99-45A5-A191-047EE33E004E@.microsoft.com...[vbcol=seagreen]
> Similar, but what I had to do was to change the compatibilty level of all
> my
> subscriptions to 2005 and I was able to add this new one back in.
> Thanks for the response.
> "Paul Ibison" wrote:
|||I scrpited out my replication as a delete and create.
I ran the delete with no issues, but when I tried to run the create that's
when I fell into the compatibilty issue.
i changed all the SQL 200 compatibity levels to 2005 and changed my script
from 80rtm to 90rtm on the create statement of the script SQl generated.
I reran the create and it created with no issues. I started my agent and
synced my data since I only care about what happens here in my main office
anything changed at my branch got overwritten if there were any changes at
both places.
Is that the same way you did yours? maybe you had a better solution, mine
seemed to work for me but I am always looking for better and different
solutions.
"Rafael Lenartowicz" wrote:
> John,
> I had very similar situation just the other day, where somebody deleted
> publication on SQL2000's level while
> there were some pubs already created in 2005's level and I needed to
> recreate the publication.
> I somehow managed to fix it, but I'm afraid I might have lost some
> unsynchronized data in the process - I'm not sure it was the best way to do
> it. Could you post step by step description how did you handle it?
> thanks,
> r
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:C284873D-DD99-45A5-A191-047EE33E004E@.microsoft.com...
>
>
|||how did you manage to change the compatibility level? using
sp_changemergepublication ?
I wasn't able to do it, it was complaining something about the incompatible
snapshot...
besides - in my setup the data from the remote location IS the vital data -
they submiting their
daily revenue reports to the central office reporting server, I can't have
anything overwritten or lost.
thanks
r
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:EE97BCC9-6445-44F4-BF33-D115DDD98B43@.microsoft.com...[vbcol=seagreen]
>I scrpited out my replication as a delete and create.
> I ran the delete with no issues, but when I tried to run the create that's
> when I fell into the compatibilty issue.
> i changed all the SQL 200 compatibity levels to 2005 and changed my script
> from 80rtm to 90rtm on the create statement of the script SQl generated.
> I reran the create and it created with no issues. I started my agent and
> synced my data since I only care about what happens here in my main office
> anything changed at my branch got overwritten if there were any changes at
> both places.
> Is that the same way you did yours? maybe you had a better solution, mine
> seemed to work for me but I am always looking for better and different
> solutions.
> "Rafael Lenartowicz" wrote:
Subscribe to:
Posts (Atom)