The list provided does not seem to provide any of the views available?
Comments
6 comments
-
Hi,
Could you be a bit more specific. E.g. what is the statement you are writing? Which views would you expect, etc. Also, which version of SQL Server are you using?
Regards,
Tilman -
I don't see any of the views or columns associated with the information_schema come up
if I do
SELECT * FROM information_schema
the information_schema comes up as part of the autocomplete but then after I put the . to reference any of the views nothing comes up. Then as you reference the columns non of those are listed.
so after I type
SELECT * FROM information_schema.col I would expect to see "columns"on the list of options. Then all the columns in the view "columns" when I start into the where statement.
I would expect all the schema views to be available. I have not seen this work in SQL2000 or SQL2005. Currently most of my work is in SQL2005.Tilman wrote:Hi,
Could you be a bit more specific. E.g. what is the statement you are writing? Which views would you expect, etc. Also, which version of SQL Server are you using?
Regards,
Tilman -
Hi,
I do get the views in the information_schema schema, in particular, the 'columns' view is there. Could it be that you don't have sufficient permissions?
Regards,
Tilman -
SELECT * FROM INFORMATION_SCHEMA.columns will execute fine.
the auto complete only shows "column". Many of the information_schema views below do not auto complete for the view name and I have not seen any column autocomplete work. This is all in SQL2005 sp1.
TABLE_PRIVILEGES
DOMAINS
SCHEMATA
ROUTINE_COLUMNS
COLUMNS
TABLE_CONSTRAINTS
KEY_COLUMN_USAGE
VIEWS
VIEW_COLUMN_USAGE
ROUTINES
DOMAIN_CONSTRAINTS
CONSTRAINT_COLUMN_USAGE
COLUMN_DOMAIN_USAGE
VIEW_TABLE_USAGE
PARAMETERS
REFERENTIAL_CONSTRAINTS
CHECK_CONSTRAINTS
TABLES
CONSTRAINT_TABLE_USAGE
COLUMN_PRIVILEGES -
I've also got SQL2005 SP1 and I get all these. Could it be that you don't have sufficient permissions?
We currently can't show columns of system views in SQL2005. This is a known issue. We will try to fix it in a future version.
Regards,
Tilman -
I am a sysadmin on this system.
Add comment
Please sign in to leave a comment.