Are the posted questions getting worse?

Question

Post reply

Are the posted questions getting worse?

Viewing 15 posts - 2,086 through 2,100 (of 66,712 total)

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

David Webb-CDS SSCoach Points: 17398 More actions · Answer 1

Incoming!!!

http://www.sqlservercentral.com/Forums/Topic665389-5-1.aspx?Update=1

And then again, I might be wrong ...
David Webb

The Dixie Flatline SSC Guru Points: 53354 More actions · Answer 2

Applause for Lynn !!!!

He actually persuaded a new OP to go back and set up their question correctly 🙂

http://www.sqlservercentral.com/Forums/Topic664360-338-1.aspx?Update=1

Strong with him was The Force.

__________________________________________________

Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills

noeld SSC Guru Points: 96590 More actions · Answer 3

noeld

SSC Guru

Points: 96590

February 26, 2009 at 6:46 pm

#950935

can't believe this "thing" is still alive

* Noel

Grant Fritchey SSC Guru Points: 398882 More actions · Answer 4

I just got directly to the page by googling '"Are the posted questions getting worse" karate'.

Apparently I was quoting Captain Queeg. It must have been right after a Cub Scout meeting, "You there, yes, you, tuck in your shirt."

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 5

Bruce W Cassidy (2/26/2009)
So what's the value of upper case?

Works better on old eyes like mine. That and...

This is very much personal preference stuff though.

Heh... correct... well... except in my shop where it's mandatory because the code designers in EM and SMS do the keywords in upper case and we're going for ease of use/consistency.

--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)

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 6

GilaMonster (2/26/2009)
Jeff Moden (2/26/2009)
All SQL Keywords in UPPER CASE.
All database names, table names, procedure names, column names, column aliases, variable names (basically, my stuff) etc, in MixedCase with no underscores. The exception to the rule of no underscores is for triggers, indexes, constraints, and references (FK's).
Table aliases and owner/schema in all lower case. Normaly kept to 5 characters or less, there's no need for underscores. Here's an example (Tally table)...
String literals as required.
Snap. Almost exactly the casing standards I use. I do sometimes get lazy when writing something quick to post.

Great minds think alike... 😛 modeled very close to what the query designers in 2k and 2k5 spit out... makes it easier for "coders" to comply.

--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)

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 7

Darwin knew this was possible...

http://www.sqlservercentral.com/Forums/Topic665342-148-1.aspx

--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)

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 8

Jeff Moden (2/26/2009)
[Great minds think alike... 😛 modeled very close to what the query designers in 2k and 2k5 spit out... makes it easier for "coders" to comply.

Not that i ever use those query designers.

Main difference from yours is that I sometimes use mixed case for aliases (especially column aliases), and I'll honour the case of the system objects. So master.dbo.sysobjects

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 9

GilaMonster (2/26/2009)
Jeff Moden (2/26/2009)
All SQL Keywords in UPPER CASE.
All database names, table names, procedure names, column names, column aliases, variable names (basically, my stuff) etc, in MixedCase with no underscores. The exception to the rule of no underscores is for triggers, indexes, constraints, and references (FK's).
Table aliases and owner/schema in all lower case. Normaly kept to 5 characters or less, there's no need for underscores. Here's an example (Tally table)...
String literals as required.
Snap. Almost exactly the casing standards I use. I do sometimes get lazy when writing something quick to post.

Same here, and almost certainly acquired from here.

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

Mark Cowne One Orange Chip Points: 26952 More actions · Answer 10

Jeff Moden (2/26/2009)
I follow the following casing standard...
All SQL Keywords in UPPER CASE.
All database names, table names, procedure names, column names, column aliases, variable names (basically, my stuff) etc, in MixedCase with no underscores. The exception to the rule of no underscores is for triggers, indexes, constraints, and references (FK's).
Table aliases and owner/schema in all lower case. Normaly kept to 5 characters or less, there's no need for underscores. Here's an example (Tally table)...
String literals as required.

Pretty much exactly what we do, I really don't like underscores...

Seems to be a common convention, don't know where it originates.

____________________________________________________

Deja View - The strange feeling that somewhere, sometime you've optimised this query before

How to get the best help on a forum

http://www.sqlservercentral.com/articles/Best+Practices/61537

Grant Fritchey SSC Guru Points: 398882 More actions · Answer 11

Jeff Moden (2/26/2009)
Darwin knew this was possible...
http://www.sqlservercentral.com/Forums/Topic665342-148-1.aspx

What? You don't know about Type II? You been living in a cave?

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 12

Same kind of coding standards we have here. One thing we always say NO NO to is using Underscore in Stored Proc names. (sp_xxx) If I see that, I go bonkers...:P

For Clustered Index it is cx_TableName__ColumnName and Index it is ix_TableName__ColumnName. We use camel case though.

-Roy

Jeff Moden SSC Guru Points: 1004329 More actions · Answer 13

Mark (2/27/2009)
Pretty much exactly what we do, I really don't like underscores...
Seems to be a common convention, don't know where it originates.

Oracle... when code is autogenned, it comes out in all uppercase for things like column names whether you want it to or not. Oracle peeps have gotten into the habit of using underscores to make things readable in autogenned code. Problem there is, they only have 30 characters per object name to boot... so they also end up having to follow an abbreviation standard instead of using whole words like "Date" (DT).

--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)

Grant Fritchey SSC Guru Points: 398882 More actions · Answer 14

Jeff Moden (2/27/2009)
Oracle... when code is autogenned, it comes out in all uppercase for things like column names whether you want it to or not. Oracle peeps have gotten into the habit of using underscores to make things readable in autogenned code. Problem there is, they only have 30 characters per object name to boot... so they also end up having to follow an abbreviation standard instead of using whole words like "Date" (DT).

And the tortured abbreviations they come up with are pretty scary. Best of all, our local Oracle DBA's try to defend the 30 character limit as a glorius design feature that keeps them from having to deal with the messy long names that we deal with on a regular basis... then I show them intellisense in 2008 or Red Gate SQL Prompt. They sputter a bit and walk away... makes my day. Tormenting Oracle DBA's is more fun than tormenting developers.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

ChrisM@Work SSC Guru Points: 186127 More actions · Answer 15

Jeff Moden (2/27/2009)
Oracle... when code is autogenned, it comes out in all uppercase for things like column names whether you want it to or not. Oracle peeps have gotten into the habit of using underscores to make things readable in autogenned code. Problem there is, they only have 30 characters per object name to boot... so they also end up having to follow an abbreviation standard instead of using whole words like "Date" (DT).

Heh tell me about it - I'm currently writing interface code between PS and an SQL2k db. The Oracle peeps throw UPPER_CASE AND UNDR_SCRD ABBRVD stuff WITHNOWHITESPACE at me all the time, and they don't understand simple stuff like UPDATE...FROM... which we take for granted. It's driving me bonkers!

^{“Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw}

For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden