Comments
1 comment
-
Hi there,
I've just been investigating this, and it turns out that our meta-data model requires users to have dbo permissions in order to be able to access certain system tables, in particular with respect to check constraints. I've managed already to locate this issue in our bug tracking system and have revved it to critical severity, however the fix for it is likely to be non-trivial as the meta-data model is a rather complex beast and is used in several of our products. This means that we obviously need to be mindful of the knock-on effects any changes might have.
My colleague who deals with this is currently out of the office, however as soon as I know more I'll let you know.
Many thanks,
Add comment
Please sign in to leave a comment.
I get the error as SQL Prompt gathers the database information. On our staging database, it looks like it stops on "Reading constraints" (though it seems to make it through everything prior to that just fine). On our production database, it stops immediately.
I'm assuming this is due to lack of proper permissions, so I guess the main topic of this discussion should be, what permissions are required by SQL Prompt in order to access the full database schema? Also, is there a way to disable various candidate types (to which we may not have permissions) so that we at least can get candidate listings for table names and column names?