User's Manual

permissible, while other changes are restrictive, and must be avoided.
The following changes must be avoided, except under the conditions stated:
♦ Change the publisher for the consolidated database.
♦ Make restrictive changes to tables, such as dropping a column or altering
a column to not allow NULL values. Changes that include the column or
including NULL entries may already be being sent in messages around
the SQL Remote setup, and will fail.
♦ Alter a publication. Publication definitions must be maintained at both
local and remote sites, and changes that rely on the old publication
definition may already be being sent in messages around the
SQL Remote setup.
You can make permissive changes, such as adding a new table or column,
as long as you use passthrough to ensure that the new table or column
exists in the remote database and in the publication at the remote
database.
♦ Drop a subscription. This can be done only if you use passthrough
deletes to remove the data at the remote site.
♦ Unload and reload an Adaptive Server Anywhere database.
If an Adaptive Server Anywhere database is participating in replication, it
cannot be unloaded and reloaded without re-synchronizing the database.
Replication is based on the transaction log, and when a database is
unloaded and reloaded, the old transaction log is no longer available. For
this reason, good backup practices are especially important when
participating in replication.
An Adaptive Server Enterprise database can be unloaded and reloaded as
long as the system is quiet and the transaction log is fully scanned. The
page_id and row_id rows in the sr_queue_state table of the stable queue
must be reset.
188