Put your schema objects (views, procs, user defined functions), in a
separate snapshot publication, and run this after your initial snapshot has
been distributed. Either that or put them in the post snapshot command.
Note that replication is supposed to order replicated objects according to
dependencies, but it refers to sysdepends for this, which if frequently
inaccurate.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com [quoted text, click to view] "Ton" <Ton@discussions.microsoft.com> wrote in message
news:24EDA244-C592-41F9-A2F3-5583AE3B19E7@microsoft.com...
> Hi All,
>
> I setup a replication from one SQL 2000 server (A) to another (B). Before
> creating a replication I scripted a database on a server A and ran a
> script
> (successfuly) on the server B. It created all tables, views, sps, etc.
> After a snapshot had been generated and synchronization begins it fails
> due
> to the error message :
> Invalid object name 'TRANSACTIONS'. (Source: MSSQLServer, Error number:
> 208)
> Get help: http://help/208
> Unable to replicate a view or function because the referenced objects or
> columns are not present on the Subscriber. (Source: MSSQLServer, Error
> number: 00000)
> Get help: http://help/00000
>
> that view (transactions) is being deleted every time replication is
> started
> but is there right after I ran a script. There is no explisit drop view
> command.
> Any suggestions?
> Thanks,
> Ton