I'm trying to filter an article by a Int field with the following
ID=CONVERT(int,HOSTNAME()), but ID=CONVERT(int,'1') works. This used to work
in previous versions.
Thanks Mike Smith
The CONVERT errors out with convertion from nvarchar to int not allowed.
Also, I know the function is HOST_NAME(). Typo.
Thanks Mike Smith
"msmith" wrote:
> I'm trying to filter an article by a Int field with the following
> ID=CONVERT(int,HOSTNAME()), but ID=CONVERT(int,'1') works. This used to work
> in previous versions.
> Thanks Mike Smith
Showing posts with label field. Show all posts
Showing posts with label field. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
Replication changing PK
I have a very strange thing happening where the primary key field is getting
changed when synchronizing with a subscriber. Background:
-Using SQL 2k and merge replication
-Testing with Publisher and Distributor on same server.
-Setup only 1 subscriber to test.
-Added a record into the Publisher into 2 tables (People and ApplicantInfo)
with a PK-FK link (1 to 1) on a field named PersonID. I also entered 9
records into a table with 1-many relationship to the ApplicantInfo table
(but not really relevant here).
-I check the records in the tables before I synchronized and both had a key
value of 195134582.
-I then synchronized from the subscriber and got the following conflict
error:
"The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted at
'DELLGX260.MCFIData'. The record can't be added or changed. Referential
integrity rules require a related record in table 'People'."
-I then opened EM and searched the People table on the Publisher and the
PersonID now has a value of 211587197.
-There is no update trigger on the People table, only delete trigger and
insert trigger. Below is the insert trigger on the People table. Could it
somehow affect the PersonID when inserting into subscriber? I hope not.
CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
SET NOCOUNT ON
DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
/* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
SELECT @.newc = (SELECT PersonID FROM inserted)
UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
Can anyone shed light on this as it is critical to implementing replication.
Thank you.
David
Turns out, the problem had to be the trigger as it fired again when synching
and changed the PersonID again. I removed the trigger and defaulted the
PersonID to random number and now it works fine.
David
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>I have a very strange thing happening where the primary key field is
>getting changed when synchronizing with a subscriber. Background:
> -Using SQL 2k and merge replication
> -Testing with Publisher and Distributor on same server.
> -Setup only 1 subscriber to test.
> -Added a record into the Publisher into 2 tables (People and
> ApplicantInfo) with a PK-FK link (1 to 1) on a field named PersonID. I
> also entered 9 records into a table with 1-many relationship to the
> ApplicantInfo table (but not really relevant here).
> -I check the records in the tables before I synchronized and both had a
> key value of 195134582.
> -I then synchronized from the subscriber and got the following conflict
> error:
> "The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted
> at 'DELLGX260.MCFIData'. The record can't be added or changed. Referential
> integrity rules require a related record in table 'People'."
> -I then opened EM and searched the People table on the Publisher and the
> PersonID now has a value of 211587197.
> -There is no update trigger on the People table, only delete trigger and
> insert trigger. Below is the insert trigger on the People table. Could
> it somehow affect the PersonID when inserting into subscriber? I hope
> not.
> CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
> SET NOCOUNT ON
> DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
> /* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
> SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
> SELECT @.newc = (SELECT PersonID FROM inserted)
> UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
>
> Can anyone shed light on this as it is critical to implementing
> replication. Thank you.
>
> David
>
|||This is actually a trigger ordering issue. Merge triggers are system
triggers and fire first. Than means your insert hit and fired the merge
trigger. Your trigger then fired causing an update to the same row which
was inserted. This will almost always cause a conflict to be thrown.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:epRwmORJGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Turns out, the problem had to be the trigger as it fired again when
> synching and changed the PersonID again. I removed the trigger and
> defaulted the PersonID to random number and now it works fine.
> David
> "David Chase" <dlchase@.lifetimeinc.com> wrote in message
> news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>
changed when synchronizing with a subscriber. Background:
-Using SQL 2k and merge replication
-Testing with Publisher and Distributor on same server.
-Setup only 1 subscriber to test.
-Added a record into the Publisher into 2 tables (People and ApplicantInfo)
with a PK-FK link (1 to 1) on a field named PersonID. I also entered 9
records into a table with 1-many relationship to the ApplicantInfo table
(but not really relevant here).
-I check the records in the tables before I synchronized and both had a key
value of 195134582.
-I then synchronized from the subscriber and got the following conflict
error:
"The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted at
'DELLGX260.MCFIData'. The record can't be added or changed. Referential
integrity rules require a related record in table 'People'."
-I then opened EM and searched the People table on the Publisher and the
PersonID now has a value of 211587197.
-There is no update trigger on the People table, only delete trigger and
insert trigger. Below is the insert trigger on the People table. Could it
somehow affect the PersonID when inserting into subscriber? I hope not.
CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
SET NOCOUNT ON
DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
/* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
SELECT @.newc = (SELECT PersonID FROM inserted)
UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
Can anyone shed light on this as it is critical to implementing replication.
Thank you.
David
Turns out, the problem had to be the trigger as it fired again when synching
and changed the PersonID again. I removed the trigger and defaulted the
PersonID to random number and now it works fine.
David
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>I have a very strange thing happening where the primary key field is
>getting changed when synchronizing with a subscriber. Background:
> -Using SQL 2k and merge replication
> -Testing with Publisher and Distributor on same server.
> -Setup only 1 subscriber to test.
> -Added a record into the Publisher into 2 tables (People and
> ApplicantInfo) with a PK-FK link (1 to 1) on a field named PersonID. I
> also entered 9 records into a table with 1-many relationship to the
> ApplicantInfo table (but not really relevant here).
> -I check the records in the tables before I synchronized and both had a
> key value of 195134582.
> -I then synchronized from the subscriber and got the following conflict
> error:
> "The row was inserted at 'LIFEDEVTEST.MCFIData' but could not be inserted
> at 'DELLGX260.MCFIData'. The record can't be added or changed. Referential
> integrity rules require a related record in table 'People'."
> -I then opened EM and searched the People table on the Publisher and the
> PersonID now has a value of 211587197.
> -There is no update trigger on the People table, only delete trigger and
> insert trigger. Below is the insert trigger on the People table. Could
> it somehow affect the PersonID when inserting into subscriber? I hope
> not.
> CREATE TRIGGER T_People_ITrig ON dbo.People FOR INSERT AS
> SET NOCOUNT ON
> DECLARE @.randc int, @.newc int /* FOR AUTONUMBER-EMULATION CODE */
> /* * RANDOM AUTONUMBER EMULATION CODE FOR FIELD 'PersonID' */
> SELECT @.randc = (SELECT convert(int, rand() * power(2, 30)))
> SELECT @.newc = (SELECT PersonID FROM inserted)
> UPDATE People SET PersonID = @.randc WHERE PersonID = @.newc
>
> Can anyone shed light on this as it is critical to implementing
> replication. Thank you.
>
> David
>
|||This is actually a trigger ordering issue. Merge triggers are system
triggers and fire first. Than means your insert hit and fired the merge
trigger. Your trigger then fired causing an update to the same row which
was inserted. This will almost always cause a conflict to be thrown.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:epRwmORJGHA.3856@.TK2MSFTNGP12.phx.gbl...
> Turns out, the problem had to be the trigger as it fired again when
> synching and changed the PersonID again. I removed the trigger and
> defaulted the PersonID to random number and now it works fine.
> David
> "David Chase" <dlchase@.lifetimeinc.com> wrote in message
> news:OA4dtoDJGHA.3120@.TK2MSFTNGP10.phx.gbl...
>
Tuesday, March 20, 2012
Replication and Timestamp
Hi,
I have a database that has tables with Timestamp field. I am trying to do a
transactional replication on this db. The wizard changed my "Subscription"
table's timestamp field to Binary format.
Now, the problem is that a report application (we didn't write it) require
this TimeStamp field as Timestamp datatype for it to work. We create the
replication mainly because of this application (we don't want it to take up
any real cpu cycle on the live server). Switching this field back to
timestamp breaks the replication.
Help...
thanks,
Alex
Hi Alex,
You may want to consider using merge replication or
transactional replication with the queued updating
option. For these replications, when articles contain a
timestamp column, the timestamp column is replicated,
but the literal timestamp values are not. The timestamp
values are regenerated when applying the initial
snapshot rows at the Subscriber. This allows timestamp
to continue using optimistic concurrency control (a
frequent usage). For snapshot and transactional
publications, and publications that allow immediate
updating, the literal values for a timestamp column are
replicated, but the data type for the replicated values
is changed to binary (8) on the Subscriber.
This information can be found at the "Data Needs and
Characteristics" topic in BOL:
http://msdn.microsoft.com/library/en...lsql/replplan_
5jub.asp
If you have any further questions, please feel free to
let me know.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>Subject: Replication and Timestamp
>Date: Thu, 9 Dec 2004 16:20:43 -0800
>Lines: 19
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57801
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Hi,
>I have a database that has tables with Timestamp field.
I am trying to do a
>transactional replication on this db. The wizard
changed my "Subscription"
>table's timestamp field to Binary format.
>Now, the problem is that a report application (we
didn't write it) require
>this TimeStamp field as Timestamp datatype for it to
work. We create the
>replication mainly because of this application (we
don't want it to take up
>any real cpu cycle on the live server). Switching this
field back to
>timestamp breaks the replication.
>Help...
>thanks,
>Alex
>
>
|||Well, it works to a point...
Here is the problem I am faced with using this new method (Queued Update
setup).
1) Snapshot works fine.
2) When Transactional Replication happens, it will error out with "Syntax
Error/Access Denied Error".
3) Error happens because the Replication Wizard created a bunch of SPs on
the subscriber. And all these SPs contain space " ", "," and "$" in its
name. Main reason is that my Table names where these SPs based on contain "
", "," and "$".
4) Before switching to Queued Update method, I have a Tab named "Command"
under the Article setup screen. Now it is gone.
If there is a way for me to change the SPs name and tell the server to use
them, I am set. Or if there is a way for me to disable all these SPs, I
will be set too...
Please Help.
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> You may want to consider using merge replication or
> transactional replication with the queued updating
> option. For these replications, when articles contain a
> timestamp column, the timestamp column is replicated,
> but the literal timestamp values are not. The timestamp
> values are regenerated when applying the initial
> snapshot rows at the Subscriber. This allows timestamp
> to continue using optimistic concurrency control (a
> frequent usage). For snapshot and transactional
> publications, and publications that allow immediate
> updating, the literal values for a timestamp column are
> replicated, but the data type for the replicated values
> is changed to binary (8) on the Subscriber.
> This information can be found at the "Data Needs and
> Characteristics" topic in BOL:
> http://msdn.microsoft.com/library/en...lsql/replplan_
> 5jub.asp
> If you have any further questions, please feel free to
> let me know.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!tk2msftngp13.phx.gbl
> microsoft.public.sqlserver.replication:57801
> I am trying to do a
> changed my "Subscription"
> didn't write it) require
> work. We create the
> don't want it to take up
> field back to
>
|||Hi Alex,
A BUG has been filed for the type of problem you are
having with replication.
Q306608 BUG: Distribution Agent May Fail with Incorrect
Syntax
http://support.microsoft.com/?id=306608
The only workaround was to rename the tables without the
special characters.
The problem is that when Logreader generates the command
it does not use delimiters. There is no way to configure
it work differently. You may consider creating the
article differently. On the publication properties,
click the ... button and uncheck the "replace
insert/update/delete..." checkboxes to force the use of
straight SQL to deliver the commands. This is also
available with scripting as options on sp_addarticle
where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
perform slower but it should work. Please give this a
try and let me know how it works for you.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Fri, 10 Dec 2004 16:13:22 -0800
>Lines: 116
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP15.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57831
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Well, it works to a point...
>Here is the problem I am faced with using this new
method (Queued Update
>setup).
>1) Snapshot works fine.
>2) When Transactional Replication happens, it will
error out with "Syntax
>Error/Access Denied Error".
>3) Error happens because the Replication Wizard
created a bunch of SPs on
>the subscriber. And all these SPs contain space " ",
"," and "$" in its
>name. Main reason is that my Table names where these
SPs based on contain "
>", "," and "$".
>4) Before switching to Queued Update method, I have a
Tab named "Command"
>under the Article setup screen. Now it is gone.
>If there is a way for me to change the SPs name and
tell the server to use
>them, I am set. Or if there is a way for me to disable
all these SPs, I
>will be set too...
>Please Help.
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
a[vbcol=seagreen]
timestamp[vbcol=seagreen]
are[vbcol=seagreen]
values[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
field.[vbcol=seagreen]
this
>
>
|||William...
Thanks for the info... But unfortunately, I cannot change the Table Name at
the source. It is because the Source tables are from Navision (Another
Microsoft Product). And Navision uses Company Name + '$" to prefix the
table names.
Any chance for there is a hot fix for it?
Thanks,
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> A BUG has been filed for the type of problem you are
> having with replication.
>
> Q306608 BUG: Distribution Agent May Fail with Incorrect
> Syntax
> http://support.microsoft.com/?id=306608
>
> The only workaround was to rename the tables without the
> special characters.
> The problem is that when Logreader generates the command
> it does not use delimiters. There is no way to configure
> it work differently. You may consider creating the
> article differently. On the publication properties,
> click the ... button and uncheck the "replace
> insert/update/delete..." checkboxes to force the use of
> straight SQL to deliver the commands. This is also
> available with scripting as options on sp_addarticle
> where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
> perform slower but it should work. Please give this a
> try and let me know how it works for you.
>
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> <XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!TK2MSFTNGP15.phx.gbl
> microsoft.public.sqlserver.replication:57831
> method (Queued Update
> error out with "Syntax
> created a bunch of SPs on
> "," and "$" in its
> SPs based on contain "
> Tab named "Command"
> tell the server to use
> all these SPs, I
> wrote in message
> a
> timestamp
> are
> values
> http://msdn.microsoft.com/library/en...lsql/replplan_
> and
> V6.00.2900.2180
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> field.
> this
>
|||If there isn't a hotfix, as a work-around you might want to consider
transactionally replicating an indexed view of the table. If the subscriber
has to use the name as the tablename - ie with the hyphen, then a 'normal'
view on the subscriber could be used at that end.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Alex,
I'm sorry that I could not find other workarounds
regarding this issue, and there is not a hotfix for now.
However, I'm glad to tell you that this issue is planned
to be fixed in the next version of SQL Server. Currently
you may consider using Snapshot replication.
Feel free to let me know if I could explain anything
further.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
<OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
<nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Mon, 13 Dec 2004 10:41:13 -0800
>Lines: 223
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <uoTwTNU4EHA.2592@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57875
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>William...
>Thanks for the info... But unfortunately, I cannot
change the Table Name at
>the source. It is because the Source tables are from
Navision (Another
>Microsoft Product). And Navision uses Company Name +
'$" to prefix the
>table names.
>Any chance for there is a hot fix for it?
>Thanks,
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
Incorrect[vbcol=seagreen]
the[vbcol=seagreen]
command[vbcol=seagreen]
configure[vbcol=seagreen]
of[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
disable[vbcol=seagreen]
contain[vbcol=seagreen]
replicated,[vbcol=seagreen]
timestamp[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
to[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
via[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
>
>
I have a database that has tables with Timestamp field. I am trying to do a
transactional replication on this db. The wizard changed my "Subscription"
table's timestamp field to Binary format.
Now, the problem is that a report application (we didn't write it) require
this TimeStamp field as Timestamp datatype for it to work. We create the
replication mainly because of this application (we don't want it to take up
any real cpu cycle on the live server). Switching this field back to
timestamp breaks the replication.
Help...
thanks,
Alex
Hi Alex,
You may want to consider using merge replication or
transactional replication with the queued updating
option. For these replications, when articles contain a
timestamp column, the timestamp column is replicated,
but the literal timestamp values are not. The timestamp
values are regenerated when applying the initial
snapshot rows at the Subscriber. This allows timestamp
to continue using optimistic concurrency control (a
frequent usage). For snapshot and transactional
publications, and publications that allow immediate
updating, the literal values for a timestamp column are
replicated, but the data type for the replicated values
is changed to binary (8) on the Subscriber.
This information can be found at the "Data Needs and
Characteristics" topic in BOL:
http://msdn.microsoft.com/library/en...lsql/replplan_
5jub.asp
If you have any further questions, please feel free to
let me know.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>Subject: Replication and Timestamp
>Date: Thu, 9 Dec 2004 16:20:43 -0800
>Lines: 19
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57801
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Hi,
>I have a database that has tables with Timestamp field.
I am trying to do a
>transactional replication on this db. The wizard
changed my "Subscription"
>table's timestamp field to Binary format.
>Now, the problem is that a report application (we
didn't write it) require
>this TimeStamp field as Timestamp datatype for it to
work. We create the
>replication mainly because of this application (we
don't want it to take up
>any real cpu cycle on the live server). Switching this
field back to
>timestamp breaks the replication.
>Help...
>thanks,
>Alex
>
>
|||Well, it works to a point...
Here is the problem I am faced with using this new method (Queued Update
setup).
1) Snapshot works fine.
2) When Transactional Replication happens, it will error out with "Syntax
Error/Access Denied Error".
3) Error happens because the Replication Wizard created a bunch of SPs on
the subscriber. And all these SPs contain space " ", "," and "$" in its
name. Main reason is that my Table names where these SPs based on contain "
", "," and "$".
4) Before switching to Queued Update method, I have a Tab named "Command"
under the Article setup screen. Now it is gone.
If there is a way for me to change the SPs name and tell the server to use
them, I am set. Or if there is a way for me to disable all these SPs, I
will be set too...
Please Help.
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> You may want to consider using merge replication or
> transactional replication with the queued updating
> option. For these replications, when articles contain a
> timestamp column, the timestamp column is replicated,
> but the literal timestamp values are not. The timestamp
> values are regenerated when applying the initial
> snapshot rows at the Subscriber. This allows timestamp
> to continue using optimistic concurrency control (a
> frequent usage). For snapshot and transactional
> publications, and publications that allow immediate
> updating, the literal values for a timestamp column are
> replicated, but the data type for the replicated values
> is changed to binary (8) on the Subscriber.
> This information can be found at the "Data Needs and
> Characteristics" topic in BOL:
> http://msdn.microsoft.com/library/en...lsql/replplan_
> 5jub.asp
> If you have any further questions, please feel free to
> let me know.
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!tk2msftngp13.phx.gbl
> microsoft.public.sqlserver.replication:57801
> I am trying to do a
> changed my "Subscription"
> didn't write it) require
> work. We create the
> don't want it to take up
> field back to
>
|||Hi Alex,
A BUG has been filed for the type of problem you are
having with replication.
Q306608 BUG: Distribution Agent May Fail with Incorrect
Syntax
http://support.microsoft.com/?id=306608
The only workaround was to rename the tables without the
special characters.
The problem is that when Logreader generates the command
it does not use delimiters. There is no way to configure
it work differently. You may consider creating the
article differently. On the publication properties,
click the ... button and uncheck the "replace
insert/update/delete..." checkboxes to force the use of
straight SQL to deliver the commands. This is also
available with scripting as options on sp_addarticle
where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
perform slower but it should work. Please give this a
try and let me know how it works for you.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Fri, 10 Dec 2004 16:13:22 -0800
>Lines: 116
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP15.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57831
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>Well, it works to a point...
>Here is the problem I am faced with using this new
method (Queued Update
>setup).
>1) Snapshot works fine.
>2) When Transactional Replication happens, it will
error out with "Syntax
>Error/Access Denied Error".
>3) Error happens because the Replication Wizard
created a bunch of SPs on
>the subscriber. And all these SPs contain space " ",
"," and "$" in its
>name. Main reason is that my Table names where these
SPs based on contain "
>", "," and "$".
>4) Before switching to Queued Update method, I have a
Tab named "Command"
>under the Article setup screen. Now it is gone.
>If there is a way for me to change the SPs name and
tell the server to use
>them, I am set. Or if there is a way for me to disable
all these SPs, I
>will be set too...
>Please Help.
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl...
a[vbcol=seagreen]
timestamp[vbcol=seagreen]
are[vbcol=seagreen]
values[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
field.[vbcol=seagreen]
this
>
>
|||William...
Thanks for the info... But unfortunately, I cannot change the Table Name at
the source. It is because the Source tables are from Navision (Another
Microsoft Product). And Navision uses Company Name + '$" to prefix the
table names.
Any chance for there is a hot fix for it?
Thanks,
Alex
"William Wang[MSFT]" <v-rxwang@.online.microsoft.com> wrote in message
news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
> Hi Alex,
> A BUG has been filed for the type of problem you are
> having with replication.
>
> Q306608 BUG: Distribution Agent May Fail with Incorrect
> Syntax
> http://support.microsoft.com/?id=306608
>
> The only workaround was to rename the tables without the
> special characters.
> The problem is that when Logreader generates the command
> it does not use delimiters. There is no way to configure
> it work differently. You may consider creating the
> article differently. On the publication properties,
> click the ... button and uncheck the "replace
> insert/update/delete..." checkboxes to force the use of
> straight SQL to deliver the commands. This is also
> available with scripting as options on sp_addarticle
> where @.ins_cmd/upd_cmd/del_cmd='SQL'. Replication will
> perform slower but it should work. Please give this a
> try and let me know how it works for you.
>
> Sincerely,
> William Wang
> Microsoft Online Partner Support
> Get Secure! - <www.microsoft.com/security>
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and
> confers no rights.
> --
> <XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> hx.gbl!TK2MSFTNGP15.phx.gbl
> microsoft.public.sqlserver.replication:57831
> method (Queued Update
> error out with "Syntax
> created a bunch of SPs on
> "," and "$" in its
> SPs based on contain "
> Tab named "Command"
> tell the server to use
> all these SPs, I
> wrote in message
> a
> timestamp
> are
> values
> http://msdn.microsoft.com/library/en...lsql/replplan_
> and
> V6.00.2900.2180
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
> field.
> this
>
|||If there isn't a hotfix, as a work-around you might want to consider
transactionally replicating an indexed view of the table. If the subscriber
has to use the name as the tablename - ie with the hyphen, then a 'normal'
view on the subscriber could be used at that end.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hi Alex,
I'm sorry that I could not find other workarounds
regarding this issue, and there is not a hotfix for now.
However, I'm glad to tell you that this issue is planned
to be fixed in the next version of SQL Server. Currently
you may consider using Snapshot replication.
Feel free to let me know if I could explain anything
further.
Sincerely,
William Wang
Microsoft Online Partner Support
Get Secure! - <www.microsoft.com/security>
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and
confers no rights.
--
>Reply-To: "Smartikat" <Smartikat@.online.nospam>
>From: "Smartikat" <Smartikat@.online.nospam>
>References: <#JaVY4k3EHA.1396@.tk2msftngp13.phx.gbl>
<XI86lfo3EHA.3956@.cpmsftngxa10.phx.gbl>
<OT5w6Yx3EHA.3236@.TK2MSFTNGP15.phx.gbl>
<nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl>
>Subject: Re: Replication and Timestamp
>Date: Mon, 13 Dec 2004 10:41:13 -0800
>Lines: 223
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <uoTwTNU4EHA.2592@.TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.replication
>NNTP-Posting-Host: 63.171.237.106
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFT NGP08.p
hx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.sqlserver.replication:57875
>X-Tomcat-NG: microsoft.public.sqlserver.replication
>William...
>Thanks for the info... But unfortunately, I cannot
change the Table Name at
>the source. It is because the Source tables are from
Navision (Another
>Microsoft Product). And Navision uses Company Name +
'$" to prefix the
>table names.
>Any chance for there is a hot fix for it?
>Thanks,
>Alex
>
>"William Wang[MSFT]" <v-rxwang@.online.microsoft.com>
wrote in message[vbcol=seagreen]
>news:nLxDm8P4EHA.1512@.cpmsftngxa10.phx.gbl...
Incorrect[vbcol=seagreen]
the[vbcol=seagreen]
command[vbcol=seagreen]
configure[vbcol=seagreen]
of[vbcol=seagreen]
and[vbcol=seagreen]
V6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p[vbcol=seagreen]
disable[vbcol=seagreen]
contain[vbcol=seagreen]
replicated,[vbcol=seagreen]
timestamp[vbcol=seagreen]
http://msdn.microsoft.com/library/en...lsql/replplan_[vbcol=seagreen]
to[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
via[vbcol=seagreen]
================================================== ===[vbcol=seagreen]
6.00.2900.2180[vbcol=seagreen]
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.p
>
>
Wednesday, March 7, 2012
replication
I have a replication b/w two servers and the table is having replication. I want to increase the length of the field(varchar) for the table on the publication database. Can i directly change the width in the design table window or is there any other way to do it?
Please help me in this issue.
Thanks in advance.No, you can't make a DDL change like that to a replicated environment unless you uninstall the replication setup or drop the article(table).|||Originally posted by bruce_Reid
I have a replication b/w two servers and the table is having replication. I want to increase the length of the field(varchar) for the table on the publication database. Can i directly change the width in the design table window or is there any other way to do it?
Please help me in this issue.
Thanks in advance.
You can add, remove column but not change properties for existing column.|||so what should i do now.Please help me in this issue|||Originally posted by bruce_Reid
so what should i do now.Please help me in this issue
exec componentsdb..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE componentsdb..myTable SET my_field_temp = my_field
exec componentsdb..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec componentsdb..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE componentsdb..myTable SET my_field = my_field_temp
exec componentsdb..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1|||Originally posted by bruce_Reid
so what should i do now.Please help me in this issue
Use the stored procedures
sp_repladdcolumn
repldropcolumn
Before you doing, make sure you have taken a backup of the database and all your subscribers are active. Sometimes it will go crazy and you have to re-setup from the scratch.
exec my_db..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field_temp = my_field
exec my_db..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec my_db..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field = my_field_temp
exec my_db..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1|||Originally posted by smasanam
Use the stored procedures
sp_repladdcolumn
repldropcolumn
Before you doing, make sure you have taken a backup of the database and all your subscribers are active. Sometimes it will go crazy and you have to re-setup from the scratch.
exec my_db..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field_temp = my_field
exec my_db..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec my_db..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field = my_field_temp
exec my_db..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1
It needs to remember about default or constraints on column if any : remove them on publisher and subscriber - add after...|||Originally posted by snail
It needs to remember about default or constraints on column if any : remove them on publisher and subscriber - add after...
Do you have any constraints like DEFAULT value or something?|||What if the column that needs to be altered has an ID-Seed implementation. Full SNAPSHOT?
Originally posted by smasanam
Use the stored procedures
sp_repladdcolumn
repldropcolumn
Before you doing, make sure you have taken a backup of the database and all your subscribers are active. Sometimes it will go crazy and you have to re-setup from the scratch.
exec my_db..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field_temp = my_field
exec my_db..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec my_db..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field = my_field_temp
exec my_db..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1|||Originally posted by TALAT
What if the column that needs to be altered has an ID-Seed implementation. Full SNAPSHOT?
First execute sp_repldropcolumn
It will show you what constraint is attached to that table
then use that name in the
alter table [table name] drop constraint
to drop that constraint
then again execute repldropcolumn to drop that column|||I have a following column that i need to alter.
COLUMN_A INT (IDENTITY SEED=1) AUTO INCREMENT.
The column is in a published table. I want to alter it to BIGINT. i.e.,
COLUMN_A BIGINT(IDENTITY SEED=1) AUTO INCREMENT.
The column has more that 1000 rows. Since we can't update an ID-Seed column explicitly, and the old values in column are being referenced by other tables. How come it's possible to get the old values of the column into the new column without dropping the publication. Also please guide if it's possible to alter a Primary-Key in a published table.
Regards!!
Please help me in this issue.
Thanks in advance.No, you can't make a DDL change like that to a replicated environment unless you uninstall the replication setup or drop the article(table).|||Originally posted by bruce_Reid
I have a replication b/w two servers and the table is having replication. I want to increase the length of the field(varchar) for the table on the publication database. Can i directly change the width in the design table window or is there any other way to do it?
Please help me in this issue.
Thanks in advance.
You can add, remove column but not change properties for existing column.|||so what should i do now.Please help me in this issue|||Originally posted by bruce_Reid
so what should i do now.Please help me in this issue
exec componentsdb..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE componentsdb..myTable SET my_field_temp = my_field
exec componentsdb..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec componentsdb..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE componentsdb..myTable SET my_field = my_field_temp
exec componentsdb..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1|||Originally posted by bruce_Reid
so what should i do now.Please help me in this issue
Use the stored procedures
sp_repladdcolumn
repldropcolumn
Before you doing, make sure you have taken a backup of the database and all your subscribers are active. Sometimes it will go crazy and you have to re-setup from the scratch.
exec my_db..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field_temp = my_field
exec my_db..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec my_db..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field = my_field_temp
exec my_db..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1|||Originally posted by smasanam
Use the stored procedures
sp_repladdcolumn
repldropcolumn
Before you doing, make sure you have taken a backup of the database and all your subscribers are active. Sometimes it will go crazy and you have to re-setup from the scratch.
exec my_db..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field_temp = my_field
exec my_db..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec my_db..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field = my_field_temp
exec my_db..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1
It needs to remember about default or constraints on column if any : remove them on publisher and subscriber - add after...|||Originally posted by snail
It needs to remember about default or constraints on column if any : remove them on publisher and subscriber - add after...
Do you have any constraints like DEFAULT value or something?|||What if the column that needs to be altered has an ID-Seed implementation. Full SNAPSHOT?
Originally posted by smasanam
Use the stored procedures
sp_repladdcolumn
repldropcolumn
Before you doing, make sure you have taken a backup of the database and all your subscribers are active. Sometimes it will go crazy and you have to re-setup from the scratch.
exec my_db..sp_repladdcolumn 'myTable', 'my_field_temp', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field_temp = my_field
exec my_db..sp_repldropcolumn 'myTable', 'my_field', null, 1, 1
exec my_db..sp_repladdcolumn 'myTable', 'my_field', 'datetime', 'all', null, 1,1
UPDATE my_db..myTable SET my_field = my_field_temp
exec my_db..sp_repldropcolumn 'myTable', 'my_field_temp', null, 1, 1|||Originally posted by TALAT
What if the column that needs to be altered has an ID-Seed implementation. Full SNAPSHOT?
First execute sp_repldropcolumn
It will show you what constraint is attached to that table
then use that name in the
alter table [table name] drop constraint
to drop that constraint
then again execute repldropcolumn to drop that column|||I have a following column that i need to alter.
COLUMN_A INT (IDENTITY SEED=1) AUTO INCREMENT.
The column is in a published table. I want to alter it to BIGINT. i.e.,
COLUMN_A BIGINT(IDENTITY SEED=1) AUTO INCREMENT.
The column has more that 1000 rows. Since we can't update an ID-Seed column explicitly, and the old values in column are being referenced by other tables. How come it's possible to get the old values of the column into the new column without dropping the publication. Also please guide if it's possible to alter a Primary-Key in a published table.
Regards!!
Subscribe to:
Posts (Atom)