Does transaction replication modify the DB

Hi,
I have used merge replication for SQL Server DBs before but not
transactional replication. We have a DB with an existing application
attached and I know that merge replication changes the DB and may break the
app (otherwise I would use it). I assume that transactional replication
does not change the user tables in the DB?
Are there any constraints on what DB designs transactional replication
supports?
Grateful for any info
Pete
Pete,
transactional replication will add a guid column if it involves upatable
subscribers, and triggers will be added. For non-updatable subscribers,
there is a schema requirement - PK on tables - but no such schema changes.
This is from the point of view of the publisher.
From the subscriber point of view, there may be some schema changes - eg
identity columns lose their identity attribute, although this is not true
for queued updating subscribers where the identity attribute may be created
with an alternative seed.
HTH,
Paul Ibison
|||Thanks that is really useful.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23yJ4u9caEHA.2812@.tk2msftngp13.phx.gbl...
> Pete,
> transactional replication will add a guid column if it involves upatable
> subscribers, and triggers will be added. For non-updatable subscribers,
> there is a schema requirement - PK on tables - but no such schema changes.
> This is from the point of view of the publisher.
> From the subscriber point of view, there may be some schema changes - eg
> identity columns lose their identity attribute, although this is not true
> for queued updating subscribers where the identity attribute may be
created
> with an alternative seed.
> HTH,
> Paul Ibison
>
|||I published sample 2 DBs with transaction replication as a test.
In one of them it added the msrepl_tran_version column to every table - when
I published another it didn't do this. I think the only difference is with
one I choose "display advanced options" in the replication wizard - then I
choose queued updating.
Can you use immediate updating if you are publishing accross an internet
(512 ADSL) connection?
Thanks
Pete
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23yJ4u9caEHA.2812@.tk2msftngp13.phx.gbl...
> Pete,
> transactional replication will add a guid column if it involves upatable
> subscribers, and triggers will be added. For non-updatable subscribers,
> there is a schema requirement - PK on tables - but no such schema changes.
> This is from the point of view of the publisher.
> From the subscriber point of view, there may be some schema changes - eg
> identity columns lose their identity attribute, although this is not true
> for queued updating subscribers where the identity attribute may be
created
> with an alternative seed.
> HTH,
> Paul Ibison
|||Pete,
imediate updating uses 2PC and DTC, ie it needs a direct and constant
connection to allow subscribers to change data. If you have this set up then
it'll be OK, otherwise you'll need queued updating subscribers.
HTH,
Paul Ibison