Very Computer

Greeting,

  The task of creating a replication over couple of disconnected client is
intersting. What is more tricky is how to maintain the store procedure
changes, data base changes over a hundred disconnected client that replicate
via SQL7. Several alternative exist on the table:
1- Upon first installation, download a synch client program that
synchronizes data, sp and schema changes.
This is a VB / SQLDMO program that accesses the database to determine the
changes that need to be done
2- Making the synch program as a series of SQL scripts available via an NT
share.
3- Setting

Greeting,

  The task of creating a replication over couple of disconnected client is
intersting. What is more tricky is how to maintain the store procedure
changes, data base changes over a hundred disconnected client that replicate
via SQL7. Several alternative exist on the table:
1- Upon first installation, download a synch client program that
synchronizes data, sp and schema changes.
This is a VB / SQLDMO program that accesses the database to determine the
changes that need to be done.
2- Making the synch program as a series of SQL scripts available via an NT
share.
3- Setting up store procedure updates via the replication model itself.

Any thoughts in this issue ?

Walid Nouh
GTE corporation

Note: I apologize for the previously incomplete message

There is only one problem with this.  It doesn't matter if you are connected
or disconnected.  Replication does not propogate DDL.  The problem that you
run into is that if you change the underlying structure for the publication,
you have to unsubscribe, drop the publication, recreate, and resubscribe.

--

Mike
New product reviews: http://www.mssqlserver.com/products
Book reviews: http://www.mssqlserver.com/books
Replication Primer: http://www.mssqlserver.com/replication
Disaster recovery plans: http://www.mssqlserver.com/backup
SYSOP PASS Discussion Forums: http://www.sqlpass.org