How to force explicit schema for created objects?

Question

Is it possible to force create statements to require an explicit schema?
When we deploy new applications, we run scripts to create tables and such in appropriate the appropriate schema. Since we always connect as ourselves, I want to minimize the possibility that I forget to put the schema and accidentally create the object in my own schema. I really don't want to have to connect as a different user, or rely on changing the current schema in login.sql or a logon trigger.
Thanks,
Matt Knowles

Answer 1

Another option would be a DDL trigger in your schema that would raise a more targeted exception if you attempt to create a table there. Obviously, that is easier to bypass, but if the concern is just that someone accidentally creates objects in the wrong schema rather than someone deciding that creating objects in their schema is something they want to do, that's probably not a concern. And if there are multiple people that could do the deployment, a DDL trigger's error message may be less likely to be confused with a quota-related error that could also indicate a problem with the script.
Justin
Edited by: Justin Cave on Jan 18, 2011 10:48 AM
I didn't see your last update before posting. I suppose a DDL trigger could parse the DDL statement itself looking for the schema qualifier and only throw an exception if the schema qualifier was missing. Not completely foolproof, of course, but parsing most DDL shouldn't be terribly difficult.