Showing posts with label default. Show all posts
Showing posts with label default. Show all posts

Wednesday, March 28, 2012

Merge Replication, going back to primary Publiser

Hello this is a simple question. I have merge replication and I followed the
following steps in
http://support.microsoft.com/default...b;en-us;321176 to set this
up. We had to turn off the PublisherA server because of the hurricanes and
the PublisherB and SubscriberA, B and C are being replicated between
themselves. Now I have PublisherA back and on-line and the replication is
stopped in PubA. To have PubA back as primary publisher again, what do I
need to do? just start synch from PublisherA and the data will be replicated
from PubA to PubB and Subscribers A,B and C and viceversa? or do I need to
do some aditional step?
Thanks in advance
Jennyfer
change the agents to point back to publisher A. remove the -SyncToAlternate
parameter.
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
"Jennyfer Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:OuvlPsX4FHA.2552@.TK2MSFTNGP10.phx.gbl...
> Hello this is a simple question. I have merge replication and I followed
the
> following steps in
> http://support.microsoft.com/default...b;en-us;321176 to set this
> up. We had to turn off the PublisherA server because of the hurricanes and
> the PublisherB and SubscriberA, B and C are being replicated between
> themselves. Now I have PublisherA back and on-line and the replication is
> stopped in PubA. To have PubA back as primary publisher again, what do I
> need to do? just start synch from PublisherA and the data will be
replicated
> from PubA to PubB and Subscribers A,B and C and viceversa? or do I need to
> do some aditional step?
> Thanks in advance
> Jennyfer
>
|||When doing this I lost many records in some tables and some tables where
almost gone in the publisher A. Now I'm bringing the missing record from
Publisher B and it takes to much time because when inserting these records
in publisher A it's trying to update them in Publisher B and subscribers.
How can I improve this, at this rate it will take me weeks to have the
databases on sync. They're thousands of records gone and why did this
happen, he just deleted important records.
thanks in advance
Jennyfer
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:Oj9rRxb4FHA.3444@.tk2msftngp13.phx.gbl...
> change the agents to point back to publisher A. remove
> the -SyncToAlternate
> parameter.
> --
> 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
> "Jennyfer Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
> news:OuvlPsX4FHA.2552@.TK2MSFTNGP10.phx.gbl...
> the
> replicated
>
|||Hello I'm sending this again since I didn't have any answer. My important
question is why thousands of records are gone? Why when switching I lost
many records? And 2 small tables that have around 500 records and are being
replicated and are not transactional records are gone too. They were gone
when trying to swicth, and they had records and those are very important
tables like stores and users tables.
Thanks
"Jennyfer Barco" <pdwhitt@.nospam.wdsinc.com> wrote in message
news:uGjsuKf5FHA.3588@.TK2MSFTNGP15.phx.gbl...
> When doing this I lost many records in some tables and some tables where
> almost gone in the publisher A. Now I'm bringing the missing record from
> Publisher B and it takes to much time because when inserting these records
> in publisher A it's trying to update them in Publisher B and subscribers.
> How can I improve this, at this rate it will take me weeks to have the
> databases on sync. They're thousands of records gone and why did this
> happen, he just deleted important records.
> thanks in advance
> Jennyfer
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:Oj9rRxb4FHA.3444@.tk2msftngp13.phx.gbl...
>

Merge Replication with Interactive Resolver

1) Can you use the Default Interactive Resolver with SQL Express and Merge
Replication ?
2) Has anyone successfully done this?
My setup is Windows XP Laptop with SQL Express, Windows Server 2003 with SQL
Server 2005 Standard. I have setup Merge Replication between the two
computers where conflict resolution is automatic.
However, whenever I try to implement Interactive Resolution I get the
following message on the laptop:
"Microsoft SQL Server 2005 (SystemPortfolioystem
Portfolio(PublicHealth1\SQLEXPRESS)): The merge process failed to get
correct information about the Interactive Resolver component from the
registry. Verify that the registry exists and that the path is correct."
Thanks in Advance!
Jeremy
Worked in SQL 2000, broken in SQL 2005.
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
"Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
news:FCE3D3A5-C3F9-4954-9870-546330D29F43@.microsoft.com...
> 1) Can you use the Default Interactive Resolver with SQL Express and Merge
> Replication ?
> 2) Has anyone successfully done this?
> My setup is Windows XP Laptop with SQL Express, Windows Server 2003 with
> SQL
> Server 2005 Standard. I have setup Merge Replication between the two
> computers where conflict resolution is automatic.
> However, whenever I try to implement Interactive Resolution I get the
> following message on the laptop:
> "Microsoft SQL Server 2005 (SystemPortfolioystem
> Portfolio(PublicHealth1\SQLEXPRESS)): The merge process failed to get
> correct information about the Interactive Resolver component from the
> registry. Verify that the registry exists and that the path is correct."
> Thanks in Advance!
> Jeremy
>
|||Do you know if there are plans to fix it in a future version/service pack?
Thanks,
Jeremy
"Hilary Cotter" wrote:

> Worked in SQL 2000, broken in SQL 2005.
> --
> 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
> "Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
> news:FCE3D3A5-C3F9-4954-9870-546330D29F43@.microsoft.com...
>
>
|||I don't have a clue. I'll ping Microsoft on it. You might want to try to do
the same.
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
"Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
news:0615B2B3-12B9-421B-A747-029180B2D42D@.microsoft.com...[vbcol=seagreen]
> Do you know if there are plans to fix it in a future version/service pack?
> Thanks,
> Jeremy
> "Hilary Cotter" wrote:
|||Also, are they any workarounds for SQL 2005.
Thanks again,
Jeremy
"Hilary Cotter" wrote:

> Worked in SQL 2000, broken in SQL 2005.
> --
> 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
> "Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
> news:FCE3D3A5-C3F9-4954-9870-546330D29F43@.microsoft.com...
>
>
|||I'll put a bug in their ear. Also, I see you have written an entire book on
SQL Server Replication so while I have an expert to ask, are you using any
workarounds for interactive conflict resolution between SQL Express and SQL
Server 2005?
It seems like a huge feature to be missing.
Thanks for your feedback!!!
Jeremy
"Hilary Cotter" wrote:

> I don't have a clue. I'll ping Microsoft on it. You might want to try to do
> the same.
> --
> 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
> "Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
> news:0615B2B3-12B9-421B-A747-029180B2D42D@.microsoft.com...
>
>
|||I'm carrying on an email conversation with the replication PM right now.
I'll keep you posted.
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
"Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
news:554B8D85-3B44-4B4D-AB5D-CD25764741CC@.microsoft.com...[vbcol=seagreen]
> I'll put a bug in their ear. Also, I see you have written an entire book
> on
> SQL Server Replication so while I have an expert to ask, are you using any
> workarounds for interactive conflict resolution between SQL Express and
> SQL
> Server 2005?
> It seems like a huge feature to be missing.
> Thanks for your feedback!!!
> Jeremy
> "Hilary Cotter" wrote:
|||Thanks, that's fantastic as I don't have very much influence with Microsoft
but will notify them anyway I can that this feature no longer works in SQL
2005.
Thanks again,
Jeremy
"Hilary Cotter" wrote:

> I'm carrying on an email conversation with the replication PM right now.
> I'll keep you posted.
> --
> 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
> "Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
> news:554B8D85-3B44-4B4D-AB5D-CD25764741CC@.microsoft.com...
>
>
|||Hilary,
I have opened a case with the Microsoft SQL Integration Support department.
I forwarded detailed instructions to duplicate the error. I'll let you know
what I hear as well.
Thanks,
Jeremy
"Hilary Cotter" wrote:

> I'm carrying on an email conversation with the replication PM right now.
> I'll keep you posted.
> --
> 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
> "Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
> news:554B8D85-3B44-4B4D-AB5D-CD25764741CC@.microsoft.com...
>
>
|||The team on my end is look at it as well.
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
"Jeremy Scrime" <JeremyScrime@.discussions.microsoft.com> wrote in message
news:BBC0DA3D-6F50-4DD0-91A4-7F70EF4D8EE9@.microsoft.com...[vbcol=seagreen]
> Hilary,
> I have opened a case with the Microsoft SQL Integration Support
> department.
> I forwarded detailed instructions to duplicate the error. I'll let you
> know
> what I hear as well.
> Thanks,
> Jeremy
>
> "Hilary Cotter" wrote:

Monday, March 26, 2012

Merge replication UNIQUEIDENTIFIER Column?

Hi all,
I am using SQL 2005 sp1 to setup Merge replication for PDA access.
i created my Primary Key column a GUID using NEWID() as the default value.
When the snapshot was created it still went and added anothe GUID to all my
tables called rowguid.
i thought it was suposed to use the existing Unique GUID column before
creating a new one?
thanks for you advice. i hope i have the corect groups here?
inkquote:
If a published table does not have a uniqueidentifier column with the
ROWGUIDCOL property and a unique index, replication adds one
So, check for the rowguidcol property...
MC
"iKiLL" <iKill@.NotMyEmail.com> wrote in message
news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
> Hi all,
> I am using SQL 2005 sp1 to setup Merge replication for PDA access.
> i created my Primary Key column a GUID using NEWID() as the default value.
> When the snapshot was created it still went and added anothe GUID to all
> my tables called rowguid.
> i thought it was suposed to use the existing Unique GUID column before
> creating a new one?
> thanks for you advice. i hope i have the corect groups here?
> ink
>|||Sorry my point was that i had created one and SQL2005 still created its own.
Now from what i can tell i think i have figgerd it out.
The behaviour i was expecting was how SQL 2000 handled the row GUID column
for snapshots.
i am using SQL 2005.
it seems that there is in fact a property of the column called RowGuid that
must be set to Yes before creating the first snapshot.
Then SQL2005 will use that column instead of creating it's own. Just setting
the data type and making it the primary key is not enough.
Thanks for your input Marko.
"MC" <marko.culoNOSPAM@.gmail.com> wrote in message
news:eruu6p$pcf$1@.ss408.t-com.hr...
> quote:
> If a published table does not have a uniqueidentifier column with the
> ROWGUIDCOL property and a unique index, replication adds one
>
> So, check for the rowguidcol property...
>
> MC
>
> "iKiLL" <iKill@.NotMyEmail.com> wrote in message
> news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
>|||Yes, you need RowGuid property. Point is, you can have any number of
uniqueidentifiers in a table, but one of them needs to have this property
set. Since SQL Server doesnt want to guess which one would you like to have
as the 'main' GUID in a table, it adds another with rowguid property set.
Offcourse, if you allready have one it doesnt need to add it.
MC
"iKiLL" <iKill@.NotMyEmail.com> wrote in message
news:e2jo3%23bWHHA.600@.TK2MSFTNGP05.phx.gbl...
> Sorry my point was that i had created one and SQL2005 still created its
> own.
> Now from what i can tell i think i have figgerd it out.
> The behaviour i was expecting was how SQL 2000 handled the row GUID column
> for snapshots.
> i am using SQL 2005.
> it seems that there is in fact a property of the column called RowGuid
> that must be set to Yes before creating the first snapshot.
> Then SQL2005 will use that column instead of creating it's own. Just
> setting the data type and making it the primary key is not enough.
> Thanks for your input Marko.
>
>
>
> "MC" <marko.culoNOSPAM@.gmail.com> wrote in message
> news:eruu6p$pcf$1@.ss408.t-com.hr...
>

Merge replication UNIQUEIDENTIFIER Column?

Hi all,
I am using SQL 2005 sp1 to setup Merge replication for PDA access.
i created my Primary Key column a GUID using NEWID() as the default value.
When the snapshot was created it still went and added anothe GUID to all my
tables called rowguid.
i thought it was suposed to use the existing Unique GUID column before
creating a new one?
thanks for you advice. i hope i have the corect groups here?
ink
Sorry my point was that i had created one and SQL2005 still created its own.
Now from what i can tell i think i have figgerd it out.
The behaviour i was expecting was how SQL 2000 handled the row GUID column
for snapshots.
i am using SQL 2005.
it seems that there is in fact a property of the column called RowGuid that
must be set to Yes before creating the first snapshot.
Then SQL2005 will use that column instead of creating it's own. Just setting
the data type and making it the primary key is not enough.
Thanks for your input Marko.
"MC" <marko.culoNOSPAM@.gmail.com> wrote in message
news:eruu6p$pcf$1@.ss408.t-com.hr...
> quote:
> If a published table does not have a uniqueidentifier column with the
> ROWGUIDCOL property and a unique index, replication adds one
>
> So, check for the rowguidcol property...
>
> MC
>
> "iKiLL" <iKill@.NotMyEmail.com> wrote in message
> news:uS1$gVbWHHA.4796@.TK2MSFTNGP05.phx.gbl...
>

Friday, March 23, 2012

Merge Replication Speed

Hello,
When I first started experimenting/testing Merge Replication about a year
ago, I found that the default Merge Replication speed seemed to be a full
minute. After doing some research, I tried creating a profile and changing
the -PollingInterval parameter from 60 to 1. This got changes moving across
about once per second (as expected.) Now, when I'm running the same tests,
I'm finding that the maximum speed seems to be once every five seconds, even
though I have again changed the -PollingInterval to 1 second.
Has something changed in a service pack in SQL where replication will go no
faster than once every five seconds? Any information would be greatly
appreciated!
Thanks, and thanks for all the help others have given me through this group
to date! It has not been insignificant!
Marshall
Merge replication's latency on a high throughput system is typical between 1
to 2 minutes. It is possible that there is more metadata in the merge
replication tables which is causing the latency to be larger than the 1 s
that it was before.
AFAIK there has been no significant change to the merge replication process
which would account for this increase in latency.
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
"Marshall Cummings" <mbcdev@.yahoo.com> wrote in message
news:1118427207.284445@.nnrp1.phx1.gblx.net...
> Hello,
> When I first started experimenting/testing Merge Replication about a year
> ago, I found that the default Merge Replication speed seemed to be a full
> minute. After doing some research, I tried creating a profile and
> changing
> the -PollingInterval parameter from 60 to 1. This got changes moving
> across
> about once per second (as expected.) Now, when I'm running the same
> tests,
> I'm finding that the maximum speed seems to be once every five seconds,
> even
> though I have again changed the -PollingInterval to 1 second.
> Has something changed in a service pack in SQL where replication will go
> no
> faster than once every five seconds? Any information would be greatly
> appreciated!
> Thanks, and thanks for all the help others have given me through this
> group
> to date! It has not been insignificant!
>
> Marshall
>

Monday, March 12, 2012

Merge replication latency

I'm a newby to SQL Server and by default is responsible for my company SQL
servers. We've a merge replication environement for 2 SQL2K databases. I
would like to know if there's a way to find and monitor the latency
frequency in this merge replication environment?
I found this great article that shows how to track latency for a
transactional replication environment.
http://databasejournal.com/features/...le.php/3441801
But have not been succesfull in converting it to a merge environment.
Thanks,
TLN