Are the posted questions getting worse?

Question

Post reply

Are the posted questions getting worse?

Viewing 15 posts - 66,721 through 66,735 (of 66,816 total)

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

DesNorton SSC-Insane Points: 24568 More actions · Answer 1

Come on @Jeff-Moden. One more post ....

How to post data/code on a forum to get the best help.

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

I'm not Jeff, but BOO!

This reply was modified 7 months ago by Brandie Tarvin. Reason: Removed weird auto-filled tag

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.

DesNorton SSC-Insane Points: 24568 More actions · Answer 3

Congratulations @jeff-moden

Finally overtook the high priestess on the SSC overall leaderboard.

How to post data/code on a forum to get the best help.

Jeff Moden SSC Guru Points: 1004646 More actions · Answer 4

DesNorton wrote:

Congratulations @jeff-moden Finally overtook the high priestess on the SSC overall leaderboard.

She did have a shedload of LIKEs. The "upgrade" on the site years ago hasn't helped much either. I do miss her posts.

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

DesNorton SSC-Insane Points: 24568 More actions · Answer 5

Jeff Moden wrote:

DesNorton wrote:
Congratulations @jeff-moden Finally overtook the high priestess on the SSC overall leaderboard.
She did have a shedload of LIKEs. The "upgrade" on the site years ago hasn't helped much either. I do miss her posts.

Indeed, it would be nice to see her back. She was the reason that I first visited SSC to look for answers.

I had the pleasure of working with her on a large ETL project when SQL 2005 was still in CTP. Very direct and to the point. Always knew where you stood.

How to post data/code on a forum to get the best help.

Jo Pattyn SSC-Dedicated Points: 32478 More actions · Answer 6

Nvidia drivers are under the weather, having an expensive video card to see black screens every so often. Not feeling the burn yet

below86 SSChampion Points: 11579 More actions · Answer 7

Is there any circumstances where you would allow code with a 'SELECT * ' to go into production?

I believe this should NEVER happen. There is a discussion that some are trying to make that if it is in a sub-query it is OK.

This came up because I was doing a code review and I told the person that the 'SELECT *' had to be fixed to list the columns selected.

I just think it's so easy now to get those values to drop in there that using an asterisk is just lazy and poor coding habits.

-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret.

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

below86 wrote:

Is there any circumstances where you would allow code with a 'SELECT * ' to go into production?
I believe this should NEVER happen. There is a discussion that some are trying to make that if it is in a sub-query it is OK.
This came up because I was doing a code review and I told the person that the 'SELECT *' had to be fixed to list the columns selected.
I just think it's so easy now to get those values to drop in there that using an asterisk is just lazy and poor coding habits.

Sure.

It's fine in a WHERE EXISTS clause.

None of the tables in our data warehouse are directly accessible to users. They can only access the tables through views that were created. The underlying tables change regularly. The views created on those tables all use SELECT * FROM table.

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/

Grant Fritchey SSC Guru Points: 399289 More actions · Answer 9

Jeff Moden wrote:

DesNorton wrote:
Congratulations @jeff-moden Finally overtook the high priestess on the SSC overall leaderboard.
She did have a shedload of LIKEs. The "upgrade" on the site years ago hasn't helped much either. I do miss her posts.

Yeah, she's missed. She nominated me for MVP back in 2008. She was always fun at events too. Hope she's happy & having fun.

"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

Grant Fritchey SSC Guru Points: 399289 More actions · Answer 10

below86 wrote:

Is there any circumstances where you would allow code with a 'SELECT * ' to go into production?
I believe this should NEVER happen. There is a discussion that some are trying to make that if it is in a sub-query it is OK.
This came up because I was doing a code review and I told the person that the 'SELECT *' had to be fixed to list the columns selected.
I just think it's so easy now to get those values to drop in there that using an asterisk is just lazy and poor coding habits.

I lean heavily towards, no, shouldn't be in production, period. Although, in the grand scheme of things, depending on the circumstances, that may not be the worst thing on its way to production, or already there. SELECT * isn't at the top of my list of worries I guess is what I'm saying. But it's on the list.

"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

Sean Lange SSC Guru Points: 286609 More actions · Answer 11

Grant Fritchey wrote:

Jeff Moden wrote:
DesNorton wrote:
Congratulations @jeff-moden Finally overtook the high priestess on the SSC overall leaderboard.
She did have a shedload of LIKEs. The "upgrade" on the site years ago hasn't helped much either. I do miss her posts.
Yeah, she's missed. She nominated me for MVP back in 2008. She was always fun at events too. Hope she's happy & having fun.

She certainly is missed. For that matter this whole site is sorely missed. The "upgrade" Jeff mentions unfortunately was what killed this once amazing niche on the internet. I learned so much from this place from some truly inspiring people. It was a shame to see if fall apart from a software project that clearly wasn't tested or thought out well enough. It was exceptionally painful to happen here, a site dedicated to technology.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

ScottPletcher SSC Guru Points: 101202 More actions · Answer 12

Michael L John wrote:

below86 wrote:

Is there any circumstances where you would allow code with a 'SELECT * ' to go into production?
I believe this should NEVER happen. There is a discussion that some are trying to make that if it is in a sub-query it is OK.
It's fine in a WHERE EXISTS clause.
None of the tables in our data warehouse are directly accessible to users. They can only access the tables through views that were created. The underlying tables change regularly. The views created on those tables all use SELECT * FROM table.

Bolded is same thing for us. Just be sure to set up something to automatically do "sp_refreshview"s when needed.

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".

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

Sean Lange wrote:

Grant Fritchey wrote:
Jeff Moden wrote:
DesNorton wrote:
Congratulations @jeff-moden Finally overtook the high priestess on the SSC overall leaderboard.
She did have a shedload of LIKEs. The "upgrade" on the site years ago hasn't helped much either. I do miss her posts.
Yeah, she's missed. She nominated me for MVP back in 2008. She was always fun at events too. Hope she's happy & having fun.
She certainly is missed. For that matter this whole site is sorely missed. The "upgrade" Jeff mentions unfortunately was what killed this once amazing niche on the internet. I learned so much from this place from some truly inspiring people. It was a shame to see if fall apart from a software project that clearly wasn't tested or thought out well enough. It was exceptionally painful to happen here, a site dedicated to technology.

Even worse, I've been "promised" many times that "people are working on things". The last promise was "just" a few months ago. We all know how that has worked out. I agree that a super-niche has been basically wiped off the face of the planet. The original change to Word Press years ago chased newbies, neophytes, and alumni away in droves... and continues to do so.

I occasionally loiter at other sites but none, including the current SSC, will ever match the old one.

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

Sergiy SSC Guru Points: 110209 More actions · Answer 14

Michael L John wrote:

below86 wrote:
Is there any circumstances where you would allow code with a 'SELECT * ' to go into production?
I believe this should NEVER happen. There is a discussion that some are trying to make that if it is in a sub-query it is OK.
This came up because I was doing a code review and I told the person that the 'SELECT *' had to be fixed to list the columns selected.
I just think it's so easy now to get those values to drop in there that using an asterisk is just lazy and poor coding habits.
Sure.
It's fine in a WHERE EXISTS clause.
None of the tables in our data warehouse are directly accessible to users. They can only access the tables through views that were created. The underlying tables change regularly. The views created on those tables all use SELECT * FROM table.

It's actually better in WHERE EXISTS clause.

I personally used "SELECT 1" until I discovered that in this case optimizer goes through column name evaluation process, when in case of SELECT * it's not invoked.

It's not a big difference, and only can be measured on tables with really big number of columns, but still...

_____________
Code for TallyGenerator

vihanrichard Newbie Points: 1 More actions · Answer 15

It depends on the platform and the user base. Some forums see a decline in question quality due to spam, repetitive queries, or lack of research before posting. However, others maintain high standards with active moderation and engaged communities. Encouraging well-structured, insightful questions can improve overall discussion quality. What do you think?