February 24, 2025 at 12:33 pm
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)
February 24, 2025 at 2:01 pm
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.
February 24, 2025 at 3:24 pm
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.
February 24, 2025 at 3:29 pm
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.
February 24, 2025 at 3:51 pm
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/
February 24, 2025 at 7:41 pm
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.
March 1, 2025 at 7:58 pm
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.
March 4, 2025 at 1:48 pm
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
March 4, 2025 at 2:00 pm
Reviving 10 year old zombie threads should probably be a no-no.
<lurch><lurch><shuffle>
"CPUUUUUUUU.... CPUUUUUUUUUU...."
"Memoreeeeeeeeeeee..."
<lurch><lurch><shuffle>
"Dataaaaaaaaa...."
March 5, 2025 at 5:05 pm
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...
March 6, 2025 at 9:53 pm
Reviving 10 year old zombie threads should probably be a no-no.
If it provides a good answer, especially a more effective good answer, I don't mind. It'll help others when they come across the old thread. Might even be one of ol' zombies that's looking for an answer... or a good laugh. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 7, 2025 at 12:58 am
Grant Fritchey wrote:Reviving 10 year old zombie threads should probably be a no-no.
If it provides a good answer, especially a more effective good answer, I don't mind. It'll help others when they come across the old thread. Might even be one of ol' zombies that's looking for an answer... or a good laugh. 😀
10 year old zombies tend to be quite cute,,,,
😎
...unless they are threads 🙂
March 20, 2025 at 3:57 pm
Anyone noticing a round of replies to posts that "feel" suspiciously like someone fed the OP's question into one of the chat-bot AIs and posted the "answer"?
March 27, 2025 at 4:10 pm
Anyone noticing a round of replies to posts that "feel" suspiciously like someone fed the OP's question into one of the chat-bot AIs and posted the "answer"?
It's not an uncommon problem. I'm finding it harder and harder to trust content (I don't just mean here), from people who weren't active 5 or more years ago, where I can at least see that they knew what they were talking about then, and so hopefully their recent content is also original. There's a lot of sites that are getting responses copied verbatim from AI, without denoting it's by AI (which most of them strongly suggest/require you do when copying from them).
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 15 posts - 66,736 through 66,750 (of 66,816 total)
You must be logged in to reply to this topic. Login to reply