Sysobjects (xType vs Type)

Question

Post reply

Sysobjects (xType vs Type)

Christopher Stobbs

SSC-Insane

Points: 21098
More actions
September 1, 2008 at 9:03 am

#212040

HI All,
What is the difference between xType and Type in sysobjects?
Thanks
Chris
----------------------------------------------
Try to learn something about everything and everything about something. - Thomas Henry Huxley
:w00t:
Posting Best Practices[/url]
Numbers / Tally Tables[/url]
SQL-4-Life

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Christopher Stobbs SSC-Insane Points: 21098 More actions · Answer 1

HI All,

It seems that xType is what should be used, Type is there for backward compatibility

If this is not 100% correct please let me know.

P.S the only value differences are

xType --> Type

PK --> K

UQ --> K

Thanks

Chris

----------------------------------------------
Try to learn something about everything and everything about something. - Thomas Henry Huxley

:w00t:
Posting Best Practices[/url]
Numbers / Tally Tables[/url]

SQL-4-Life

Perry Whittle SSC Guru Points: 234013 More actions · Answer 2

indeed the whole table is there for backward compatibility, the SQL2005 table is sys.objects

You will also find some other sys------- tables which are for backward compatibility too

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

Jeff Moden SSC Guru Points: 1004434 More actions · Answer 3

Christopher Stobbs (9/1/2008)
Type is there for backward compatibility

I wonder why some of the folks from Redmond saw fit to use it to define some of the information schema views if it's there just for backward compatibility. Yeah, I know what they say, but there it is in THEIR code. 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)