Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Rules! Expand / Collapse
Author
Message
Posted Wednesday, November 18, 2009 10:15 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, July 23, 2013 6:34 AM
Points: 654, Visits: 265
Comments posted to this topic are about the item Rules!
Post #821362
Posted Thursday, November 19, 2009 9:10 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, July 17, 2014 10:56 AM
Points: 3,924, Visits: 1,607
sysrules in option. Good way to Trick.

Never seen object like this.


SQL DBA.
Post #821707
Posted Thursday, November 19, 2009 12:07 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:36 PM
Points: 5,565, Visits: 24,699
Having recently gotten my brains beat out, my integrity questioned, my intelligence derided and other wise vilified (Refer to the QOD 11/17/2009 forum). I am greatly surprised that the little bitty nitpickers are not raging here in this forum, perhaps it is because they do not intimately know enough about SQL Server or since they got the message they so dearly love to see, that is "You got it right".

But let me point out a technicality: The question asked which of these views would you query. The correct answer as given is sysobjects.

Now for the sorry bit of fact the displayed item: sysobjects is a SYSTEM TABLE
The VIEW is sys.sysobjects. Which of course contains essentially the same data as does the system table. To be more specific it is defined as a CATALOG VIEW, but a view nevertheless.

Now this should not be attributed as an effort to denigrate the author of this QOD, knowing how hard it is to compose an "acceptable" QOD.
VM-723206 I congratulate you on your adroit side stepping the nit pickers.



If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read

Before posting a performance problem please read
Post #821861
Posted Thursday, November 19, 2009 1:58 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 11:59 AM
Points: 5,916, Visits: 8,165
bitbucket-25253 (11/19/2009)
Having recently gotten my brains beat out, my integrity questioned, my intelligence derided and other wise vilified (Refer to the QOD 11/17/2009 forum). I am greatly surprised that the little bitty nitpickers are not raging here in this forum, perhaps it is because they do not intimately know enough about SQL Server or since they got the message they so dearly love to see, that is "You got it right".

But let me point out a technicality: The question asked which of these views would you query. The correct answer as given is sysobjects.

Now for the sorry bit of fact the displayed item: sysobjects is a SYSTEM TABLE
The VIEW is sys.sysobjects. Which of course contains essentially the same data as does the system table. To be more specific it is defined as a CATALOG VIEW, but a view nevertheless.


If you are going to pick nits, make sure you get your facts right.

In SQL Server 2000 and older versions, sysobjects was indeed a system table. But as of SQL Server 2005, system tables are no longer exposed. They have been replaced by system views, of which sys.objects (that is, the view named objects in the schema named sys) is an example.

To preserve compatibility with older versions, a second set of views, the so-called compatibility views, were introduced. One of those views is sys.sysobjects. And to preserve full compatibility, SQL Server will find this view even if you omit the schema name and shorten it to just sysobjects.

So, unless you assumed the question to be about SQL Server 2000 or before, you picked the wrong nit. For in all current versions of SQL Server, sysobjects is indeed a view, not a table.

The true nitpicker though, would have complained about something else - and that is that the real true answer is not included. Books Online includes a note with all compatibility views that these will be removed in a future version of SQL Server, and that the current SQL Server system views should be used instead. So the only really correct answer would have been to query the sys.objects view.



Hugo Kornelis, SQL Server MVP
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Post #821944
Posted Thursday, November 19, 2009 4:28 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 9:46 PM
Points: 21,187, Visits: 14,880
While these are valid arguments about nit-picking of questions, one vital piece of information was overlooked. This question was only worth 1 point.

Bitbucket, your question was worth more points. Had it only been 1 point, there would have been far less picking.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #822011
Posted Thursday, November 19, 2009 10:00 PM


SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Friday, January 11, 2013 12:41 PM
Points: 621, Visits: 297
Hey this was easy one. Hope for more such easy Q's in future!



Bhavesh Patel

http://bhaveshgpatel.wordpress.com/
Post #822092
Posted Friday, November 20, 2009 7:46 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, July 18, 2014 12:13 PM
Points: 2,837, Visits: 1,138
You could quibble that the complete rule is not stored in sysobjects, since the rule definition is in syscomments. But sysobjects is the best answer of the choices given.


Post #822408
Posted Wednesday, December 2, 2009 2:33 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, November 5, 2013 6:08 AM
Points: 1,079, Visits: 591
Beaten but a leeson learned should never be learned again.

What you don't know won't hurt you but what you know will make you plan to know better
Post #827272
Posted Saturday, December 5, 2009 9:48 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Thursday, June 5, 2014 10:54 AM
Points: 9,902, Visits: 9,480
Yes, could we please stop asking QotD's that only have correct answers for SQL Server 2000?

-- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
Proactive Performance Solutions, Inc.
"Performance is our middle name."
Post #829498
Posted Wednesday, January 6, 2010 7:14 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 10:05 AM
Points: 7,045, Visits: 6,784
RBarryYoung (12/5/2009)
Yes, could we please stop asking QotD's that only have correct answers for SQL Server 2000?


Now that is nit-picking



Far away is close at hand in the images of elsewhere.

Anon.

Post #842773
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse