Viewing 15 posts - 46 through 60 (of 59,063 total)
I know this is an old post but thought I'd add a little constructive feedback as to why folks may have graded it low.
If used for 100 rows, the data...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 9, 2025 at 11:49 pm
Nice article.
TBH though, there are a lot of things listed as "disadvantages" for these 3 datatypes that I also wish you couldn't do with the newer MAX datatypes. I also...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2025 at 5:47 pm
I doubt that anybody (besides some old, long retired boomer nerds that implented it decades ago) are using COLUMNS_UPDATED(), particularly since
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2025 at 12:31 pm
The question specifically states "I want to determine if both the CustomerContactFirstName and CustomerContactLastName fields are changed, but no others. "
That means that the first answer cannot be correct...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2025 at 12:26 pm
Just to be sure...
Anyone with "db_owner" privs on a database can see, use, and manipulate any and all objects in the database, regardless of who owns the individual objects because...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2025 at 12:10 pm
The number of 30102777 is NOT a row count... it's a PAGE COUNT (1 logic read = 1 8KB page) If you divide that number by 128 (the number of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2025 at 5:38 am
Although Ola's code has been branded as the "Gold Standard" by good people like Paul Randal, I won't use his code for index maintenance because it measures the wrong things...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2025 at 3:59 am
COLUMNS_UPDATED() will tell you which columns had an update attempted but it will not tell you if a value actually changed.
Also, I'm in favor of the clarity of IF UPDATED(CreditLimit)...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2025 at 3:31 am
It returned some headers so none of the answers is actually correct.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2025 at 3:28 am
Practice SQL interactively, https://www.sql-practice.online/ This is perfect for SQL interview prep. No signup required - just start practicing!
I have Norton Utilities and Global Protect running... one of them didn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 16, 2025 at 3:20 am
For example, if you were planning to use the "Import Data" wizard. That's there in 20, and prior, but not in 21
What on Earth are they thinking?
Lordy...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 13, 2025 at 2:45 pm
Just to add to the advice - I would advise against SELECT * unless it is absolutely necessary. The reason being if the source metadata changes (column added or...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 12, 2025 at 10:17 pm
I have to give Steve a huge amount of credit for my success... he's kept this site going and he encouraged me to write articles. This site was also a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2025 at 9:53 pm
However, when the query SELECT * FROM LS01.DB01.dbo.vwA is executed directly on Server B (targeting the linked server), the same operation takes approximately 50 seconds to complete.
We had similar...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2025 at 9:25 pm
In some cases, indexes can hurt SELECT performance. .
Do you have a link on that subject?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 9, 2025 at 3:05 am
Viewing 15 posts - 46 through 60 (of 59,063 total)