Comments
Sort by recent activity
The solution works once but if I reuse the list I always have to check the list of databases to make sure that none have been added. Not truely all available databases. / comments
The solution works once but if I reuse the list I always have to check the list of databases to make sure that none have been added. Not truely all available databases.
Just revisiting this post since it has been painful to me again through a period of rapid database existence changes both adds and removes. I think this would be a great feature to be able to add all databases or all "user" databases like the feature available in maintence plans for a SQL Server instance. Having storable lists of servers is great unless you have to check them every time you runa script to make sure none are missing or extras that no longer exist. / comments
Just revisiting this post since it has been painful to me again through a period of rapid database existence changes both adds and removes. I think this would be a great feature to be able to add a...
I am a sysadmin on this system. / comments
I am a sysadmin on this system.
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
/ comments
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 ...
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 / comments
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...
I too would like to be able to specify the table that gets referenced first in the ON statement.
I'd like to see the joins go BOTH ways if possible. I actually prefer doing <table I'm joining to>.col = <table I'm joining from>.col. A small semantic difference, but just the way I like to write my SQL.
/ comments
I too would like to be able to specify the table that gets referenced first in the ON statement.
I'd like to see the joins go BOTH ways if possible. I actually prefer doing <table I'm joining to>....