Hi,
Is there a way to add the "not for replication" option to
an identity field without rebuilding the entire table.
Thanks in advance.
try something like this
http://groups.google.com/groups?selm...&output=gplain
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"kb" <anonymous@.discussions.microsoft.com> wrote in message
news:483501c4a09d$12b8ff40$a301280a@.phx.gbl...
> Hi,
> Is there a way to add the "not for replication" option to
> an identity field without rebuilding the entire table.
> Thanks in advance.
|||Many thanks Hilary,
I needed this for a DB that is approaching 1TB right now
and a full table rebuild was not an option.
Thanks agin.
>--Original Message--
>try something like this
>http://groups.google.com/groups?selm...0TK2MSFTNGP12=
..phx.gbl&output=3Dgplain
>--=20
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>"kb" <anonymous@.discussions.microsoft.com> wrote in message
>news:483501c4a09d$12b8ff40$a301280a@.phx.gbl...
>
>.
>
|||Hilary Cotter wrote:
> try something like this
> http://groups.google.com/groups?selm...&output=gplain
>
Hilary,
Many thanks again for your help.
Everything worked as expected on my test system after turning on (not
for replication) as per the above article. However on the production
system after following exactly the same steps, replication still fails
with the 'cannot insert identity when identity_insert is off' problem.
I have checked that the table's identity column is 'identity yes (not
for replication'.
I'm sure I'm missing something really stupid here, as I am able to get
one system (SQL developer) to work whilst the production system (SQL
enterprise) fails.
Any pointers as to where to go from here would be appreciated.
TIA
Ken.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment