Viewing 15 posts - 46 through 60 (of 59,069 total)
Sorry I'm lat on this thread and I may have missed it but no one is talking about the licensing costs of the SQL Server on the separate machine.
Also, did...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2025 at 5:38 pm
When you want it 100% correct, you should use ORIGINAL_LOGIN().
Especially when, IMHO, people use that nasty little word of "audit" like they did in this question.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 7, 2025 at 1:40 am
This can be done by creating database level triggers and can seriously be enhanced in capturing not only what changed when but by who from where.
I can't offer the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 17, 2025 at 5:30 am
i have a database with 400 stored porcedure , i need to optimise it , i found that tables are not having command index also.
like joins where ,group by...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2025 at 8:14 pm
Great question. Proof that extra features always come at a price. 😀
It also means more page splits than normal due to "ExpAnsive" UPDATEs because of the typical extra 4 bytes...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2025 at 6:19 pm
Btw, I disagree with those who suggest to always specify the windowing range. The default is ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW. Why repeat it? The best part...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2025 at 3:12 am
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
Viewing 15 posts - 46 through 60 (of 59,069 total)