> > How is classic currently handling metadata changes, any changes?
> >
> Table changes are handled through a table existence lock that must be
> held exclusively to change the table. Getting that exclusive lock
> requires signaling all other holders, who mark their copy of the table
> as needing to be refreshed.

Can't such a mechanism be extended/created for SPs?

Is it needed at all? (as in: did someone check yet how plans work
with SPs?)

> Index changes are handled through locks on the index root page for the
> table.
>
> Foreign key changes, up to now, require exclusive access to the database
> to avoid exactly the problems with classic.
>
> There's nothing inherently wrong with classic, and it will be our
> salvation as we move into clusters, but it does require a bit more care.

With regards,

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS SQL
Server
Upscene Productions
http://www.upscene.com