Are the posted questions getting worse?

Question

Are the posted questions getting worse?

Viewing 15 posts - 66,766 through 66,780 (of 66,808 total)

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

Sean Lange SSC Guru Points: 286602 More actions · Answer 1

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: 101186 More actions · Answer 2

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: 1004577 More actions · Answer 3

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 4

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 5

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?

jasona.work SSC Guru Points: 50165 More actions · Answer 6

I may be seeing through rose-colored glasses, but it does seem that since the switch to WP, the spam went up significantly.

I won't blame the change to the new back-end for my lack of engagement here, that was more because of things going on at work that kept me from being as active.

And, honestly, there's a certain "charm" to an old-school style forum (OK, and yes, responsiveness of the site does have some bearing, this just "feels" slower to move through)

frederico_fonseca SSCoach Points: 16208 More actions · Answer 7

some changes on forums are acceptable - SQL ServerCentral change from old format was a "soft" change and not a "I will never use this again" change.

I used to be a active member of Tek-Tips until a few month ago when they completely changed their forum format (different software maker) - since that change I refuse to use their site as layout is rather annoying, and usability compared to prior software is now a complete shit experience.

had a similar change happen here I would also leave/(had left) for good.

below86 SSChampion Points: 11562 More actions · Answer 8

Sergiy wrote:

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

I was asking about a subquery, not a view or a where exists. The subquery table being selected only had 8 columns in it, to leave in a SELECT * in that case seems unacceptable to me.

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

Phil Parkin SSC Guru Points: 247137 More actions · Answer 9

I was asking about a subquery, not a view or a where exists.

That wasn't clear, given that the first two sentences of your original post were this:

Is there any circumstances where you would allow code with a 'SELECT * ' to go into production?
I believe this should NEVER happen.

This reply was modified 1 month, 3 weeks ago by Phil Parkin.

Michael L John One Orange Chip Points: 27077 More actions · Answer 10

So, Wednesday, a member of our Infrastructure team asks me if my DBA group is the owner of an Azure database. I told him that is not a database, it is a resource group, and it contains storage accounts for non-production backups. I directed him to the person ON HIS TEAM that normally handles these things.

Thursday, another member of the SAME Infrastructure group asks me the same question. This time, I asked why, what are you trying to do? He said that there are Azure Advisor Recommendations that they are going to put in place. I told him that most of the thing on this list make little sense to implement, and they needed to do some significant testing and cost calculations for the things that they think they need to do.

I said you need to reach out within the Infrastructure group. He asked "Do you know who I can talk to in the infrastructure group?" I sent a screen shot of his department tree.

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/

below86 SSChampion Points: 11562 More actions · Answer 11

Phil Parkin wrote:

I was asking about a subquery, not a view or a where exists.
That wasn't clear, given that the first two sentences of your original post were this:
Is there any circumstances where you would allow code with a 'SELECT * ' to go into production?
I believe this should NEVER happen.

You are correct Phil, my mistake. Thanks for calling me out. I appreciate it. I get caught up in the issue I'm dealing with and forget to read everything, even what I wrote. LOL

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

frederico_fonseca SSCoach Points: 16208 More actions · Answer 12

starting to get annoyed with this user https://www.sqlservercentral.com/forums/user/srinivasdba19

been posting scripts (and not his own for sure) as reply to a whole bunch of threads - some of the scripts are even incorrect as copied from other sites.

in my opinion these type of replies with such significant volume should be reported as spam.

Grant Fritchey SSC Guru Points: 399014 More actions · Answer 13

Reviving 10 year old zombie threads should probably be a no-no.

"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

Brandie Tarvin SSC Guru Points: 173103 More actions · Answer 14

Grant Fritchey wrote:

Reviving 10 year old zombie threads should probably be a no-no.

"CPUUUUUUUU.... CPUUUUUUUUUU...."

"Memoreeeeeeeeeeee..."

"Dataaaaaaaaa...."

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.

jasona.work SSC Guru Points: 50165 More actions · Answer 15

It seems my tolerance for low-effort (in general) from people has taken a nose dive over the last 5-6 years...

Witness my rather "short" response to this question: https://www.sqlservercentral.com/forums/topic/splitting-text-based-on-certain-phrases-in-string#post-4551920

The fun part? I've had no interaction with json until some recent blog posts (I don't even recall where,) and then a quick copy/paste of Steve's code to see if I was right about what would work for the OP...