HostWeb Forums » Microsoft Databases » microsoft.public.sqlserver.replication » Adding a column to a replicated table
Topic: Re: Adding a column to a replicated table
Basically the ddl cannot include a default, identity, or constraint.
"JDS" <admin@jeremysage.com> wrote in message
news:95662527-0b3d-467d-adf0-e3eb86b77785@j22g2000hsf.googlegroups.com...
> What are the restrictions on modifying the structure of a replicated
> table?
>
> I have added columns in the past and synchronised clients after the
> modification and the modifications seem to have been picked up OK (on
> the clients). However, I have also experienced problems with expired
> subscriptions giving errors stating that the new snapshot is different
> in structure to the existing database.
>
> Before I look into this in more detail to run some trials and get the
> exact error messages, I wanted to find out what I should be expecting
> and know what the limitations are. In a way the behaviour above is
> understandable; i.e. a synchronisation can pick up modifications to
> structure but a new snapshot can't, but is this the case - is it 'by
> design' or inevitable?
>
> (Merge replication on SQL Server 2005 Workgroup edition, server acting
> as publisher and distributor; clients SQL Server 2005 Express, pull
> subscription, web synchronisation).
>
> Thanks in advance
> Jeremy.
Replies below ↓
Replies
Adding a column to a replicated table
What are the restrictions on modifying the structure of a replicated
table?
I have added columns in the past and synchronised clients after the
modification and the modifications seem to have been picked up OK (on
the clients). However, I have also experienced problems with expired
subscriptions giving errors stating that the new snapshot is different
in structure to the existing database.
Before I look into this in more detail to run some trials and get the
exact error messages, I wanted to find out what I should be expecting
and know what the limitations are. In a way the behaviour above is
understandable; i.e. a synchronisation can pick up modifications to
structure but a new snapshot can't, but is this the case - is it 'by
design' or inevitable?
(Merge replication on SQL Server 2005 Workgroup edition, server acting
as publisher and distributor; clients SQL Server 2005 Express, pull
subscription, web synchronisation).
Thanks in advance
Jeremy.
Re: Adding a column to a replicated table
On 9 Jun, 20:44, "Hilary Cotter" <hilary.cot...@gmail.com> wrote:
> Basically the ddl cannot include a default, identity, or constraint."JDS" <ad...@jeremysage.com> wrote in message
>
> news:95662527-0b3d-467d-adf0-e3eb86b77785@j22g2000hsf.googlegroups.com...
>
>
>
> > What are the restrictions on modifying the structure of a replicated
> > table?
>
> > I have added columns in the past and synchronised clients after the
> > modification and the modifications seem to have been picked up OK (on
> > the clients). However, I have also experienced problems with expired
> > subscriptions giving errors stating that the new snapshot is different
> > in structure to the existing database.
>
> > Before I look into this in more detail to run some trials and get the
> > exact error messages, I wanted to find out what I should be expecting
> > and know what the limitations are. In a way the behaviour above is
> > understandable; i.e. a synchronisation can pick up modifications to
> > structure but a new snapshot can't, but is this the case - is it 'by
> > design' or inevitable?
>
> > (Merge replication on SQL Server 2005 Workgroup edition, server acting
> > as publisher and distributor; clients SQL Server 2005 Express, pull
> > subscription, web synchronisation).
>
> > Thanks in advance
> > Jeremy.- Hide quoted text -
>
> - Show quoted text -
Thanks Hilary,
Does that mean that if I have added a column, subject to the
restrictions you have stated, and the subscription expires requiring a
new snapshot, it should then still synchronise OK (assuming that the
new snapshot is generated successfully)?