When we script our replication creation and push the initial snapshot, at
times it wants to create the views first before the tables,etc.. and want to
know how to create them in order. I was hoping SQL would be smart enough to
do so.. and now we have to create seperate publications that include one for
tables and push that first.. and another for indexed views and yet another
for views and push them sequentially once it gets created on the subscriber.

We are using SQL 2005.

You could have a look at the @processing_order parameter for merge articles.
That's the only way I know of. However having a separate publication for
views is preferable anyway for my case - that way you can reinitailize the
views if necessary quite independantly of the data.
HTH,
Paul Ibison

Is that parameter used for transactional replication ?

[quoted text, click to view]

Just merge :(
Cheers,
Paul Ibison

This is the reason why we have so many publications for many published
databases on the same publisher and starting many of those in parallel
causes deadlocks.


[quoted text, click to view]

Hassan - I'm not too sure what you're starting in parallel. Is this the
normal synchronization ie the distribution agents or are you referring to
the creation of snapshots. Is it the view creation (original topic
description) that causes the problem, or is it data-related?
Cheers,
Paul Ibison