Viewing 15 posts - 286 through 300 (of 59,099 total)
Jeff. I'll take a crack at your question:
In your example, are you assuming the date column is indexed and would be used? What if that is not the case,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 11, 2024 at 7:15 am
Jeff, with RCSI enabled, it’s barely if ever necessary.
Agreed... all you have to do there is accept an extra 14 bytes per row and extra usage of TempDB. Since...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2024 at 4:05 am
On what grounds?
Uh, because the data is right, and the implementation is right.
You set up a straw man, where this condition applies, and you don't care about this,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2024 at 4:04 am
The responses are as expected... some hardcore "NEVER"s.
To those people, I ask, if you want a simple report, say the number of products purchased by day for the previous calendar...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 10, 2024 at 1:14 am
With regard to the following code from the article...
CREATE PROCEDURE dbo.GetDashboardStats
AS
BEGIN
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
SELECT
(SELECT COUNT(*) FROM Orders WITH (NOLOCK)
WHERE OrderDate = CAST(GETDATE() AS...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2024 at 1:46 am
It's gotten to the point where I evaluate changes by determining how much harm the change causes or how little a required change brings to the table compared to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 9, 2024 at 1:08 am
Just do a test.
SET STATISTICS TIME,IO ON:
Put code to be tested here.
SET STATISTICS TIME,IO OFF:
Do NOT use this method if any functions that contain the word BEGIN...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2024 at 6:51 pm
Using YEAR and MONTH Functions:
I'm going to seriously recommend NOT doing it that way. Use the Date Range method, instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2024 at 6:02 pm
You do realize that the addition of the new index requires space that might not have been available and that dropping the first NCI made a bunch of space available,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2024 at 5:51 pm
EDIT: Looks like Steve posted while I was working on replies. Leaving this reply here even though it overlaps with Steve's pose.
FOR and AFTER are identical in meaning.
https://learn.microsoft.com/en-us/sql/t-sql/statements/create-trigger-transact-sql#arguments
You're trigger is...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2024 at 5:42 pm
From the article:
And most people rarely upgrade their OSS. They get something that works and don't want to change. I get that, as I feel the same way...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2024 at 5:11 pm
You can simplify the WHERE clause in AlphaNumericOnly and AlphaOnly by taking advantage of the fact that upper and lower case letters differ only by the 6th bit, which...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2024 at 7:58 pm
I'm a little late here but great observation, Anthony. I'll have to give that a try.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2024 at 6:57 pm
...even Microsoft stuff has to go through a testing / peep process here.
From the looks of things, MS hasn't done a good job on QA since 2017.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2024 at 10:12 pm
Does Example 7 of the following article do it for you?
https://www.mssqltips.com/sqlservertip/2999/different-ways-to-find-sql-server-object-dependencies/
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2024 at 2:35 pm
Viewing 15 posts - 286 through 300 (of 59,099 total)