| David Fishburn 2005-07-22, 9:26 am |
| "Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
news:33jsd1p50vkbtkb
vt82o0qfhbvpb66n2n1@
4ax.com of
sybase.public.sqlanywhere.mobilink:
BC> Should 9.0.2 sp_hook_dbmlsync_sch
ema_upgrade drop all non-dbmlsync
BC> connections, if it is going to alter a table that is not in the
BC> publication? (A modified version of p_drop_other_connect
ions could do
BC> the dropping)
BC>
BC> In this case, I am not sure if dbmlsync -d will help. AFAIK if some
BC> other connection has a shared schema lock on table X, and the
BC> sp_hook_dbmlsync_sch
ema_upgrad_e procedure tries to ALTER TABLE X, the
BC> hook connection will be blocked.
Hmm.
That procedure is called automatically when it is safe to do so (from a
synchronization perspective).
I believe the onus will be on you to code this routine to account for
situations you are aware of. So yes, you should force the other
connections to be dropped.
I would not want sp_hook_dbmlsync_sch
ema_upgrad to do it automatically
since a lot of people run with LockTables = OFF.
--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng9 -v).
EBFs and Maintenance Releases
http://downloads.sybase.com/swx/sdmain.stm
Developer Community / Whitepapers
http://www.ianywhere.com/developer
CaseXpress - to report bugs
http://casexpress.sybase.com
CodeXchange - Free samples
[url]http://ianywhere.codexchange.sybase.com/servlets/ ProjectDocumentList[
/url]
|