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 |
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
 Posted - 2006-02-23 : 23:21:21
|
| Hi all, Having a bit of a dilemma here... We're using the aforementioned view to check on design changes in our databases. I've just come across an instance where the datatype returned in I_S.C doesn't agree with that in syscolumns. For this given column, I_S.C reports INT where syscolumns reports an XType of 167 (varchar). Syscolumns is correct. Is there anything I can do to refresh I_S.C without restarting the server??? Is there any precendence of this sort of thing? It's happening on SQL2000 Personal, SP2 on an XP machine.Cheers,Tim |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2006-02-23 : 23:40:13
|
| What happens if you drop and recreate the view ? Does the problem persist ?Damian"A foolish consistency is the hobgoblin of little minds." - Emerson |
 |
|
|
timmy
Master Smack Fu Yak Hacker
1242 Posts |
Posted - 2006-02-24 : 00:22:26
|
| Found it....Seems that the LOCAL_TYPE_NAME on master.dbo.spt_datatype_info was wrong for the given data type (varchar, or xtype=167)Got me absolutely stumped as to why it's like that.... |
|
|
|
|
|
|
Is INFORMATION_SCHEMA.COLUMNS wrong?