Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
 Posted - 2002-02-21 : 12:12:51
|
| Ok gang, I've got one for ya!I can run this query fine on SQL7:SELECT *FROM INFORMATION_SCHEMA.COLUMNSI can run it fine from a clean install of Personal Edition SQL2K. However, it won't run on an upgraded SQL2K standard edition.I found this knowledge base article: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294350 which seems to say this is a bug AND it's by design. That didn't seem to make much sense to me.I've tried their workaround and it didn't work around. Their workaround seems to be to use the datbase before you run the query. That makes no sense at all. I'm running this as dbo and not sa. I've got a second person having the same problem except.Has anyone seen this before or discovered a work around? According to the MS knowledge base article this was last updated in October 2001. So if it's a bug, why wasn't it fixed in a service pack?===============================================Creating tomorrow's legacy systems today.One crisis at a time. |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-21 : 12:34:49
|
Graz,I have never seen this problem, and I don't know of a workaround, but I can answer you last question.They didn't fix it because it was deemed 'By Design' which means it is working the way the developers wanted it to work.It is classified as a bug, because whomever discovered it, filed it as a bug, and the developers looked at it and said, "this is what we wanted to happen" and close the bug as "By Design". So there is nothing to fix in a service pack, because it is working as they expected (Please don't blame me, I didn't come up with these rules, that's just how it works)  .If you want, you can call PSS, they will come up with a workaround for you, and your case will be free, because it is a bug. You can also ask that the file a DCR (Design Change Request) so that the design is changed in either a service pack, or in Yukon.HTH-Chad |
 |
|
|
ToddV
Posting Yak Master
218 Posts |
Posted - 2002-02-21 : 15:39:43
|
| Graz,When they say by design in this case, they mean only that the views do not exist in each of the user databases. You should however be able to run SELECT *FROM INFORMATION_SCHEMA.COLUMNSfrom any database without a problem (kind of like the sp_ stored procedures). If this select statement does not work from user databases, you have a differnet problem then this bug describes. |
|
|
|
sbradk
Starting Member
8 Posts |
Posted - 2002-02-21 : 15:45:22
|
quote:
You should however be able to run SELECT * FROM INFORMATION_SCHEMA.COLUMNSfrom any database without a problem (kind of like the sp_ stored procedures). If this select statement does not work from user databases, you have a differnet problem then this bug describes.
I've tested this in a few places and the results are inconsistent. On Personal Edition I can get results from that query. On Standard Edition (fresh installs - not upgrades) I can get results on some servers but I get "Invalid object name 'INFORMATION_SCHEMA.COLUMNS'." on others.If you do not think that KB article is related, do you have any thoughts why that view can't be seen on some servers?~bk |
|
|
|
ToddV
Posting Yak Master
218 Posts |
Posted - 2002-02-21 : 15:59:21
|
quote:
If you do not think that KB article is related, do you have any thoughts why that view can't be seen on some servers?~bk
Unfortunately, no. |
|
|
|
|
|
|
|
|
Information Schema Views