Re: Identity columns problem in replication among n no of subscribers
- From: "SANJAY PAWAR" <sanju@xxxxxxxxxx>
- Date: Mon, 13 Nov 2006 19:55:50 +0530
Dear friend Hilary
Thanks for your full co-operation. My all doubts are clear now except below
2.
1. If I am having file called EMP with identity column Recid.
I want to give automatic range control on publisher for n no. subscribers
what will be the command ?
2. If I give range 1001 to 2000 to subscriber1, will he (subscriber1) be
able to store or pull others data range from 1 to 1000 or 2001 to 3000.
Best Regards
Sanjay
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:u5x4t7MBHHA.4428@xxxxxxxxxxxxxxxxxxxxxxx
You certainly can, so you can go to your subscriber and do a
dbcc('mytablename', checkident, reseed, 10000000) and it will probably
work. However you will always have to monitor the range you assigned and
adjust it as necessary.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"SANJAY PAWAR" <sanju@xxxxxxxxxx> wrote in message
news:%23e4pfjMBHHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
Dear Friend Hilary
Thanks for the help.
But one more solution can be there if I give different IDENTITY ranges to
each subscribers.
Pls help me If you know how to give diff IDENTITY ranges to each
subscriber.
Thanks in Advance
Best Regards
Sanjay
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:ut$xlYMBHHA.4292@xxxxxxxxxxxxxxxxxxxxxxx
You will have to create different identity seeds and an increments of 2
on both sides - on the subscriber a seed of 2 with an increment of 2,
and on the publisher an seed of 1 with an increment of 1.
Make sure the identity column has the not for replication property on
it. Then set your articles up to not modify the existing tables on the
subscriber and in your pre-snapshot script have your table creation
scripts (along with their respective indexes).
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"SANJAY PAWAR" <sanju@xxxxxxxxxx> wrote in message
news:OUx4ONMBHHA.4472@xxxxxxxxxxxxxxxxxxxxxxx
I have created Transaction Replication.
Nearly 100's of tables there in my database.
I have created Recordid (identity) column with primary key in each
table and all are incremented by 1.
Front End application in VB6 is 100% dependable on this column. Changes
in this column may spoil my work of VB6.
Synchronisation is done @ subscribers side using below activex
component in VB6
Set objSQLDist = CreateObject("SQLDistribution.SQLDistribution.2")
Subscribers side does not show identity columns with primary key. It
shows only name of the column as INT.
Front application is failed to run @ subscribers side.
Pls suggest how to Replicate identity column among n no. of
subscribers.
Best Regards
Sanjay
.
- Follow-Ups:
- Re: Identity columns problem in replication among n no of subscribers
- From: Hilary Cotter
- Re: Identity columns problem in replication among n no of subscribers
- References:
- Identity columns problem in replication among n no of subscribers
- From: SANJAY PAWAR
- Re: Identity columns problem in replication among n no of subscribers
- From: Hilary Cotter
- Re: Identity columns problem in replication among n no of subscribers
- From: SANJAY PAWAR
- Re: Identity columns problem in replication among n no of subscribers
- From: Hilary Cotter
- Identity columns problem in replication among n no of subscribers
- Prev by Date: Re: MSRepl_Commands
- Next by Date: Re: The replication Merge Agent failed to retrieve subscription partit
- Previous by thread: Re: Identity columns problem in replication among n no of subscribers
- Next by thread: Re: Identity columns problem in replication among n no of subscribers
- Index(es):
Relevant Pages
|