all groups > sql server replication > january 2004 >
You're in the

sql server replication

group:

Problem in Replication



Problem in Replication niitmalad
1/21/2004 12:29:29 AM
sql server replication: Dear Friends

While creating the replication i have got the following=20
alerts in the wizard of Replication kindly suggest what=20
action i have to take so taht the replication will go=20
smooth. I am fresh for the replication so please do not=20
mind if the question is simple.

Thanks in advance.
NIITMALAD

************************************

Because this publication does not allow updatable=20
subscriptions, when IDENTITY columns are transferred to=20
the Subscriber, the IDENTITY property will not be=20
transferred. (For example, a column defined as INT=20
IDENTITY at the Publisher will be defined as INT at the=20
Subscriber.)=20

If you want the IDENTITY property transferred to the=20
subscription table, you must do the following:=20

=BB Create the subscription table manually using the=20
IDENTITY property and the NOT FOR REPLICATION option. You=20
can have SQL Server execute a custom script to perform=20
this action before the snapshot is applied. To specify a=20
custom script, create the publication, create the script,=20
and enter the script name on the Snapshot tab of the=20
publication properties.=20

=BB Set the name conflicts article property so that=20
SQL Server does not drop an existing table when applying=20
the snapshot at the Subscriber. This property is on the=20
Snapshot tab of article properties.=20

The following published tables contain IDENTITY columns:

=09
[dbo].[2002_MainInvoice]
[dbo].[2002_MAINMENU]
[dbo].[~TMPCLP99921]


SQL Server requires that all tables referenced by=20
published views and indexed views be available at the=20
Subscriber. If the referenced tables are not published as=20
articles in this publication, they must be created at the=20
Subscriber manually.=20

The following view and indexed views are published in=20
this publication:

[dbo].[DebitNoteMainChargesPerContract]
[dbo].[DebitNoteMainInvoice]
=09
SQL Server requires that all objects referenced by=20
published stored procedures, such as tables and user-
defined functions, be available at the Subscriber. If the=20
referenced objects are not published as articles in this=20
publication, they must be created at the Subscriber=20
manually.=20

The following stored procedures are published in this=20
publication:

[dbo].[CallDetailsForusers]
[dbo].[CountryRates]
=09
Create a transactional publication from=20
database 'MobistarInvoices'.

The following types of Subscribers may subscribe to this=20
publication:
Servers running SQL Server 2000

Publish the following tables as articles:
'2002_MainInvoice' as '2002_MainInvoice'
'2002_MAINMENU' as '2002_MAINMENU'
'~TMPCLP99921' as '~TMPCLP99921'

Publish the following stored procedures as articles:
'DebitNoteCallDetails' as 'DebitNoteCallDetails'
'DebitNoteIndianUsers' as 'DebitNoteIndianUsers'
=09
The name of this publication is 'MobistarInvoices'. The=20
description is 'Transactional publication of=20
MobistarInvoices database from Publisher EXCHANGE.'.

Do not filter data in this publication.

Do not allow anonymous subscriptions to this publication.

Run the Snapshot Agent at the following scheduled times:
Occurs every 1 day(s), at 23:15:00., ending 20/01/2004
Run the Snapshot Agent as scheduled.


RE: Problem in Replication chandra NO[at]SPAM online.microsoft.com
1/21/2004 6:32:41 PM
Hi -
This is just an information generated while creating the
replication. Since few of your articles has IDENTITY columns, the wizard is
just giving information about the identity property not being copied onto
the subscriber. You can go ahead and create the replication.

Regards,
Chandra
--------------------
||Content-Class: urn:content-classes:message
||From: "niitmalad" <niitmalad@yahoo.co.in>
||Sender: "niitmalad" <niitmalad@yahoo.co.in>
||Subject: Problem in Replication
||Date: Wed, 21 Jan 2004 00:29:29 -0800
||Lines: 99
||Message-ID: <16c401c3dff8$affa8460$a001280a@phx.gbl>
||MIME-Version: 1.0
||Content-Type: text/plain;
|| charset="iso-8859-1"
||Content-Transfer-Encoding: quoted-printable
||X-Newsreader: Microsoft CDO for Windows 2000
||Thread-Index: AcPf+K/468UHHx5zRK+PROnBQXuKjg==
||X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
||Newsgroups: microsoft.public.sqlserver.replication
||Path: cpmsftngxa07.phx.gbl
||Xref: cpmsftngxa07.phx.gbl microsoft.public.sqlserver.replication:46643
||NNTP-Posting-Host: tk2msftngxa08.phx.gbl 10.40.1.160
||X-Tomcat-NG: microsoft.public.sqlserver.replication
||
||Dear Friends
||While creating the replication i have got the following
||alerts in the wizard of Replication kindly suggest what
||action i have to take so taht the replication will go
||smooth. I am fresh for the replication so please do not
||mind if the question is simple.
||Thanks in advance.
||NIITMALAD
||************************************
||Because this publication does not allow updatable
||subscriptions, when IDENTITY columns are transferred to
||the Subscriber, the IDENTITY property will not be
||transferred. (For example, a column defined as INT
||IDENTITY at the Publisher will be defined as INT at the
||Subscriber.)
||If you want the IDENTITY property transferred to the
||subscription table, you must do the following:
|| » Create the subscription table manually using the
||IDENTITY property and the NOT FOR REPLICATION option. You
||can have SQL Server execute a custom script to perform
||this action before the snapshot is applied. To specify a
||custom script, create the publication, create the script,
||and enter the script name on the Snapshot tab of the
||publication properties.
|| » Set the name conflicts article property so that
||SQL Server does not drop an existing table when applying
||the snapshot at the Subscriber. This property is on the
||Snapshot tab of article properties.
||The following published tables contain IDENTITY columns:
||
|| [dbo].[2002_MainInvoice]
|| [dbo].[2002_MAINMENU]
|| [dbo].[~TMPCLP99921]
||SQL Server requires that all tables referenced by
||published views and indexed views be available at the
||Subscriber. If the referenced tables are not published as
||articles in this publication, they must be created at the
||Subscriber manually.
||The following view and indexed views are published in
||this publication:
|| [dbo].[DebitNoteMainChargesPerContract]
|| [dbo].[DebitNoteMainInvoice]
||
||SQL Server requires that all objects referenced by
||published stored procedures, such as tables and user-
||defined functions, be available at the Subscriber. If the
||referenced objects are not published as articles in this
||publication, they must be created at the Subscriber
||manually.
||The following stored procedures are published in this
||publication:
|| [dbo].[CallDetailsForusers]
|| [dbo].[CountryRates]
||
||Create a transactional publication from
||database 'MobistarInvoices'.
||The following types of Subscribers may subscribe to this
||publication:
|| Servers running SQL Server 2000
||Publish the following tables as articles:
|| '2002_MainInvoice' as '2002_MainInvoice'
|| '2002_MAINMENU' as '2002_MAINMENU'
|| '~TMPCLP99921' as '~TMPCLP99921'
||Publish the following stored procedures as articles:
|| 'DebitNoteCallDetails' as 'DebitNoteCallDetails'
|| 'DebitNoteIndianUsers' as 'DebitNoteIndianUsers'
||
||The name of this publication is 'MobistarInvoices'. The
||description is 'Transactional publication of
||MobistarInvoices database from Publisher EXCHANGE.'.
||Do not filter data in this publication.
||Do not allow anonymous subscriptions to this publication.
||Run the Snapshot Agent at the following scheduled times:
||Occurs every 1 day(s), at 23:15:00., ending 20/01/2004
||Run the Snapshot Agent as scheduled.
||
AddThis Social Bookmark Button