Home > Archive > SQL Anywhere Mobile > July 2005 > Should sp_hook_dbmlsync_schema_upgrad­e drop all non-dbmlsync connections?









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Should sp_hook_dbmlsync_schema_upgrad­e drop all non-dbmlsync connections?
Breck Carter [TeamSybase]

2005-07-20, 9:24 am

Should 9.0.2 sp_hook_dbmlsync_sch
ema_upgrade drop all non-dbmlsync
connections, if it is going to alter a table that is not in the
publication? (A modified version of p_drop_other_connect
ions could do
the dropping)

In this case, I am not sure if dbmlsync -d will help. AFAIK if some
other connection has a shared schema lock on table X, and the
sp_hook_dbmlsync_sch
ema_upgrad_e procedure tries to ALTER TABLE X, the
hook connection will be blocked.

Breck


--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com