>-----Original Message-----
>The log reader reads transactions that are committed to
the database after
>the snapshot agent has bcp'd the data out to the
snapshot. Nothing is
>missed, guaranteed.
>
>I posted something for you to try to generate the
snapshot using the custom
>sync object. Does it work?
>
>--
>Hilary Cotter
>Looking for a book on SQL Server replication?
>http://www.nwsu.com/0974973602.html
>
>
>"ChrisR" <anonymous@discussions.microsoft.com> wrote in
message
>news:975f01c48619$a87ec080$a601280a@phx.gbl...
>> sql2k sp3
>>
>> Howdy kids. Well by now you know the story as good as I
>> do. The Subscriber has more columns than the Publisher.
>> example:
>>
>> Publisher:
>> [TransDate] [smalldatetime] NULL ,
>>
>>
>> Subscriber:
>> [TransDate] [smalldatetime] NULL ,
>> [TransDateShort] [char] (10) COLLATE
>> SQL_Latin1_General_CP1_CI_AS NULL ,
>> [TransDateMonth] [tinyint] NULL ,
>> [TransDateYear] [smallint] NULL ,
>>
>> So, I can write procs to handle the inserts and updates
>> after the initial snapshot is done. But for that initial
>> snapshot Ive got problems. No matter how I get the data
to
>> the Subscriber (dts, insert...select, etc.) , how do I
>> keep the Subscriber in sync? In other words, while Im
>> doing my initial population, data will be coming into
the
>> Publisher? How do my process' tell the difference
>> betwenn "snapshot" and "new" data? I really don't want
to
>> do this off hours. This cant be a new scenario.
>>
>> TIA, ChrisR
>>
>
>
>.