"Chris" <Chris@discussions.microsoft.com> wrote in message
news:C6DF01F9-B425-491A-BD5A-DB276B908FAC@microsoft.com...
>
> Run
>
> exec sp_addsubscription @publication = 'pubNameHere'
> , @article = 'all'
> , @subscriber = 'subscrNameHere'
> , @destination_db = 'dbNameHere'
> , @sync_type = 'none' -- this will start repl w/out snapshot
> , @reserved='internal' --SQL2005
> GO
>
> Exec the following to get stored proc text for repl tables, then execute
> output at subscbriber.
>
> exec sp_scriptpublicationcustomprocs @publication = 'fxDB6_Pub1'
>
>
> A backup & restore is your snapshot - I sp_addsubscr first, then backup,
> ship, then restore, add sp's, then start distribution agent(s).
>
> ChrisB MCDBA
> www.MSSQLConsulting.com
>
>
>
> "Ryan Hanisco" wrote:
>
>> Hey everyone,
>>
>> I have geographically distributed databases where I am replicating some
>> tables between SQL 2005 instances via a transactional push replication.
>> Because of the size of the DB and some network speed issues, running a
>> snapshot is not possible as it causes downtime.
>>
>> I am 100% certain that the source and destination on these tables are
>> identical and I need to start the replication again without
>> reinitializing
>> and sending the snapshot across the wire. I do have a copy of the source
>> DB
>> that was backed up and restored on the other end of the wire that I can
>> use
>> as a data reference if need be.
>>
>> Please Help...
>>
>> --
>> Ryan Hanisco
>> MCSE, MCTS: SQL 2005, Project+
>> http://www.techsterity.com
>> Chicago, IL
>>
>> Remember: Marking helpful answers helps everyone find the info they need
>> quickly.