Hello there

In snapshot replication, all the tables that replicated are being created
whith the schema on the publisher

All the properties of the tables are being transfered exept: Primary key and
constraints

Is there a way to transfare this data also?

Roy,
on the article properties (elipsis button) there is a snapshot tab and the
checkbox option to include DRI. As far as I recall this also takes the
Defaults.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Whell Paul

I have no problem with defaults. I have do problem with primary key

Today i have script of my database, and i'm running it on the subscriber,
which also reset the data.

Then on the Snapshot tab i set the option "Keep the tables unchanged".

At this way, when the data on the subscriber has being changed, not by the
replicatio. i need to delete all the data from the subscriver and run the
snapshot again.

Is there a way to prevent it?

[quoted text, click to view]

Sorry Roy, I didn't quite follow this. Do you need the subscriber data to
remain? Are updates allowed at the subscriber? Do you want these removed or
to be sent to the publisher, then removed?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Whell Paul

This is what i want.

At the first replication, to transfare all the data and schema from the
publisher to subscriber.

Then every night to transfare the changes.

Some times, when the data on the subscriber is changed, to allow the
replication to work as whell it worked before and not get lots of bugs as a
result of changes on the subscriber that didn't do by the replication.


--
øåòé âåìãäîø
òúéã äðãñú úåëðä
èì' 03-5611606
ôìà' 050-7709399
àéîééì: roy@atidsm.co.il
[quoted text, click to view]

Roy,
transactional replication will transfer all the schema on initializationa nd
the changes on synchronization. However the data on the subscriber is to be
treated as read-only. There is really no easy option in this regard. If the
subscriber is to be allowed to alter the data, and you don't want any errors
to be raised, the data changes must go to the publisher to maintain data
consistency, so you are talking about updating subscribers - immediate or
queued. The -SKIPERRORS parameter could be used but this is a messy option.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)