>-----Original Message-----
>We are running SQL7 on both boxes, it's an intranet
environment, we
>have two servers running Windows 2000 Server about 100
miles apart.
>
>I have set up a transactional publication to push a pub
of a DB from
>our production server to a standby "failover" server that
is in a
>remote location.
>
>It's more of a spare server than true failover (there is
nothing to
>automatically make the switch, we would have to change
DNS, etc). What
>we need, though, is this server to stay up-to-date and in
sync with
>the running production server's DB, autonomously. This
means all data,
>tables, view, sprocs (def and results), unique keys,
relationships,
>contraints, default values - basically the whole shebang.
>
>The transactional publication is nice for keeping the
data up-to-date,
>but it doesn't update the schema when a change has been
made to the
>source DB (adding/dropping tables, adding fields, etc.).
I've noticed
>the publication doesn't even make the destination tables
schema
>correct (like primary keys, default values, nulls,
relationships, etc)
>which we sometimes depend on in our web applications.
>
>Is there any way I can do this?
>.