Are the posted questions getting worse?

Question

Are the posted questions getting worse?

Viewing 15 posts - 66,151 through 66,165 (of 66,815 total)

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

Brandie Tarvin SSC Guru Points: 173108 More actions · Answer 1

Looks like I woke everyone up this morning. Heeeheee.

@=)

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Grant Fritchey SSC Guru Points: 399278 More actions · Answer 2

Thom A wrote:

For someone that does provide as much content as he does/has, I can completely understand how that can wear away your sanity. 😉

Exactly. I totally understand why he does it and, as I said, I wouldn't damage a friendship over such trivial crap. However, I certainly do poke the bear on occasion. Meanest Canadian I know. Ha!

"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

ZZartin SSC-Dedicated Points: 30921 More actions · Answer 3

Thom A wrote:

Brandie Tarvin wrote:
Forget leading commas. Let's debate leading semi-colons. @=)
.Please no >_< .Leading commas I accept as a preference, but leading semicolons are another matter entirely, lol .Those are like starting every sentence with a full stop, and not ending your last sentence with one

/shrug I blame the interpreter for this. SQL Server is perfectly happy with some statements not being terminated by a semi colon, including the very statements that require the previous statement to be terminated by a semi colon. This effectively makes semi colons a statement beginner in some cases and not a true statement terminator.

ScottPletcher SSC Guru Points: 101200 More actions · Answer 4

I use

;WITH

just to help prevent possible errors. Sure, I could be technically correct and blame someone else when there was a problem with the code, but I prefer to avoid the problem altogether. Someone making a quick fix in a proc sometimes just writes a line of code without fully examining all the other code around it -- because they don't need to do that to add their particular code fix. Should they still use a ;? Sure, but it's not always required so most people don't routinely code them. I don't want a major client to have a problem in production because of something that trivial. The time to parse an extra ; is so small it can't even be measured.

SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".

Steve Jones - SSC Editor SSC Guru Points: 738556 More actions · Answer 5

I prefer:

;


-- ^
-- |
-- |
-- semi colon above because most of you don't use them
WITH mycte ....

Thom A SSC Guru Points: 99143 More actions · Answer 6

I will admit, and though I know it shouldn't, it does amuse me when I see code that has something like this:

SELECT *
FROM dbo.MyTable MT ;WITH (NOLOCK)
     JOIN dbo.YourTable YT ;WITH (NOLOCK) ON MT.ID = YT.MTID

Or even "better":

SELECT *
FROM (;WITH CTE AS(
            SELECT *,
                   ROW_NUMBER() OVER (PARTITION BY SomeCol ORDER BY ID) AS RN
            FROM dbo.MyTable)
       SELECT *
       FROM CTE
       WHERE RN = 1) DT
WHERE SomeCol > 5

It's that some people seem to think it's a ;WITH clause, rather than just WITH with a statement "beginningator" that really sells me against the syntax.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

Jonathan AC Roberts SSCoach Points: 18407 More actions · Answer 7

What I find extremely frustrating is when someone writes SQL code that joins multiple tables without prefixing the column names with their originating table or alias using dot notation. This adds a significant amount of time to the task of determining which columns belong to which tables.

Jeff Moden SSC Guru Points: 1004635 More actions · Answer 8

Grant Fritchey wrote:

Jeff Moden wrote:
David Burrows wrote:
Jeff Moden wrote:
David Burrows wrote:
That’s why I like you Jeff, you’re such a smart guy 😍🥳
Heh... if I were really smart, I'd just up and retire. That would probably kill me though.
Just like me 😂, glad I didn’t. You’ll out live us all 😀 you’re an institution you know 😃
I think most folks would say your confused, David. They rather think I should be IN an institution. 😀 😀 😀
Second!!
All in favor?
And you know I'm kidding.

Kidding??? Why??? We were going to invite you to join us! 😀 😀 😀

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

frederico_fonseca SSCoach Points: 16249 More actions · Answer 9

Jeff Moden wrote:

Grant Fritchey wrote:
Jeff Moden wrote:
David Burrows wrote:
Jeff Moden wrote:
David Burrows wrote:
That’s why I like you Jeff, you’re such a smart guy 😍🥳
Heh... if I were really smart, I'd just up and retire. That would probably kill me though.
Just like me 😂, glad I didn’t. You’ll out live us all 😀 you’re an institution you know 😃
I think most folks would say your confused, David. They rather think I should be IN an institution. 😀 😀 😀
Second!!
All in favor?
And you know I'm kidding.
Kidding??? Why??? We were going to invite you to join us! 😀 😀 😀

by the looks of it WE are ALL in one already (SSC)

Jeff Moden SSC Guru Points: 1004635 More actions · Answer 10

Phil Parkin wrote:

Brandie Tarvin wrote:
Forget leading commas. Let's debate leading semi-colons. @=)
This could start a flame war! I've seen instances of otherwise-seasoned coders on here using the dreaded
;WITH CTE AS (
pattern, as if it's the right thing to do.

Heh... leading or trailing semi-colons... I solved that problem a really long time ago (it's why they pay me the big bucks 😀 )...

I don't end code with a semi-colon nor do I start it with one... Instead, and with some exceptions (too long to explain here but there's actually a method to my madness), I put semi-colons on their own line at the beginning of a line instead of using a blank line between queries.

That does 2 things... it's real easy to see that I remembered to add them and it satisfies both the leading and training semi-colon likes, dislikes, and eventual flame wars. 😀

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

Jack Corbett SSC Guru Points: 184394 More actions · Answer 11

Not dropping temp tables at the end of stored procedures is one of the pre-requisites to take advantage of the tempdb improvements made to limit metadata contention in tempdb, https://learn.microsoft.com/en-us/archive/blogs/sql_server_team/tempdb-files-and-trace-flags-and-updates-oh-my#metadata-contention. I've seen this contention at a couple of clients in the last year and have had to recommend code changes so that they could get those benefits.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Jack Corbett SSC Guru Points: 184394 More actions · Answer 12

Jack Corbett wrote:

Not dropping temp tables at the end of stored procedures is one of the pre-requisites to take advantage of the tempdb improvements made to limit metadata contention in tempdb, https://learn.microsoft.com/en-us/archive/blogs/sql_server_team/tempdb-files-and-trace-flags-and-updates-oh-my#metadata-contention. I've seen this contention at a couple of clients in the last year and have had to recommend code changes so that they could get those benefits.

Oops, this was reply to Lynn's comment about dropping/not dropping temp tables at the end of stored procedures and it has been so long since I've posted I forgot that you have to do Quote not Reply to include the post you are replying in your post.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Thom A SSC Guru Points: 99143 More actions · Answer 13

Jonathan AC Roberts wrote:

What I find extremely frustrating is when someone writes SQL code that joins multiple tables without prefixing the column names with their originating table or alias using dot notation. This adds a significant amount of time to the task of determining which columns belong to which tables.

Gail's No, this is not a bug in T-SQL is such a great example of why it's such a bad habit. I've seen multiple instances of people saying the data engine is bugged, and it's the exact problem she outlines.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

Thom A SSC Guru Points: 99143 More actions · Answer 14

Jonathan AC Roberts wrote:

What I find extremely frustrating is when someone writes SQL code that joins multiple tables without prefixing the column names with their originating table or alias using dot notation. This adds a significant amount of time to the task of determining which columns belong to which tables.

Gail's No, this is not a bug in T-SQL is such a great example of why it's such a bad habit. I've seen multiple instances of people saying the data engine is bugged, and it's the exact problem she outlines.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

Michael L John One Orange Chip Points: 27079 More actions · Answer 15

frederico_fonseca wrote:

Jeff Moden wrote:
Grant Fritchey wrote:
Jeff Moden wrote:
David Burrows wrote:
Jeff Moden wrote:
David Burrows wrote:
That’s why I like you Jeff, you’re such a smart guy 😍🥳
Heh... if I were really smart, I'd just up and retire. That would probably kill me though.
Just like me 😂, glad I didn’t. You’ll out live us all 😀 you’re an institution you know 😃
I think most folks would say your confused, David. They rather think I should be IN an institution. 😀 😀 😀
Second!!
All in favor?
And you know I'm kidding.
Kidding??? Why??? We were going to invite you to join us! 😀 😀 😀
by the looks of it WE are ALL in one already (SSC)

I think we could get a group rate at a sanitarium.

Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/