February 8, 2023 at 1:19 am
kaj wrote:Jeff Moden wrote:kaj wrote:Jeff Moden wrote:It apparently cannot make the distinction between "temp tables" and "temporary tables". It's seriously incorrect for what most of us refer to as "temp tables" and seriously correct for "real" "Temporary Tables".
Hmm.. not sure what you're referring to with "temp tables", so I'm obviously not "most people". 🙂
Is it a temperature table? A temperamental table? A temptation table? I'm honestly wondering...
In the context of SQL Server, I personally think most people would indeed think of "temp tables" as a lazy short-hand for "temporary tables".
Totally true and we (including you) usually mean something created in TempDB whose hame starts with a "#".. ChatGTP didn't consider it as "Temporary table objects that live in TempDB that start with # sign". It was apparently thinking of a "Table created in any database that is a real table and won't automatically be dropped at the end of the session or procedure run".
Yes, and I now see your wisdom. 🙂 I think I got stuck on the sentence "It can't make the distinction between "temp tables" and "temporary tables", which didn't make much sense to me at the time.
BTW... we had a similar bit of confusion in real life at work. They wanted to create some "temporary logging tables" by run for a kind of complex system they developed. They original started out by creating them as tables with date included in the name but they had them all in the "dbo" schema. Not fun to look at in the Object Explorer. There was also great confusion between "Temp" tables (the kind in TempDB with a # sign) and the "temporary" tables they were actually talking about.
To solve both of those issues, we started calling those table "scratch" tables and made a separate schema for them to get them out of the way in the Object Explorer (which also made using a filter easier, to boot). I checked with everyone and they all agreed that they weren't needed after 7 days so I created a proc that would add a "To_Be_Deleted" prefix to those scratch tables 7 days after their last "modified" date and then those are simply dropped after 7 days.
To date, no one has ever needed to rename or use even one of the "To_Be_Deleted" tables and so we're now considering just doing the auto-drop after 7 days without the rename thing.
That’s why I like you Jeff, you’re such a smart guy 😍🥳
Far away is close at hand in the images of elsewhere.
Anon.
February 8, 2023 at 1:27 am
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.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2023 at 1:37 am
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 😃
Far away is close at hand in the images of elsewhere.
Anon.
February 8, 2023 at 1:45 am
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. 😀 😀 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2023 at 3:10 am
Jeff Moden wrote:I think most folks would say your confused, David. They rather think I should be IN an institution. 😀 😀 😀
LOL. Maybe we could be in the same room and debate leading commas. FOTFL 😜
😀
--Jeff Moden
Change is inevitable... Change for the better is not.
February 8, 2023 at 12:14 pm
Forget leading commas. Let's debate leading semi-colons. @=)
February 8, 2023 at 12:18 pm
Don't get me started in WITH (NOLOCK). Apparently there are a number of people suddenly making that recommendation to get rid of blocking.
It's apparently easier advice to give people than details on how to actually fix their code.
Always has been.
"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
February 8, 2023 at 12:18 pm
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
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
February 8, 2023 at 12:20 pm
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.
"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
February 8, 2023 at 12:22 pm
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
THIS ^^^^^^^^^^^^^^^^^^^^^!!
"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
February 8, 2023 at 12:22 pm
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
THIS ^^^^^^^^^^^^^^^^^^^^^!!
"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
February 8, 2023 at 12:24 pm
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.
A good friend, Aaron Bertrand, does it for all his demo scripts. However, he has a good reason (even if I don't agree). Because people are more than a bit ignorant about the use of semi-colons, for his examples, he always puts it at the front so that they can copy & paste it and it will always work. I think he's modelling bad behavior, like having SELECT * in example code (something I used to do). He disagrees. I'm not losing a friendship over it, but I do occasionally poke him on it.
"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
February 8, 2023 at 12:43 pm
A good friend, Aaron Bertrand, does it for all his demo scripts. However, he has a good reason (even if I don't agree). Because people are more than a bit ignorant about the use of semi-colons, for his examples, he always puts it at the front so that they can copy & paste it and it will always work. I think he's modelling bad behavior, like having SELECT * in example code (something I used to do). He disagrees. I'm not losing a friendship over it, but I do occasionally poke him on it.
I had a very similar, albiet it breif, conversation with him on this last year as well. I was on the same side as you, I don't agree with it, but I do understand why he does it.
Honestly, it's more frustrating that when someone who "copy pastas" code from somewhere and gets the error Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon. That instead of reading the error (as the problem is literally spelt out in the it), they just proclaim that the code they're copied, and have not taken the time to understand, is wrong and broken. /sigh
For someone that does provide as much content as he does/has, I can completely understand how that can wear away your sanity. 😉
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
Viewing 15 posts - 66,136 through 66,150 (of 66,816 total)
You must be logged in to reply to this topic. Login to reply