Viewing 15 posts - 451 through 465 (of 59,063 total)
Do a COUNT on both columns using GROUP BY and add a HAVING where the COUNT(*) = 1.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2024 at 5:07 am
I saw the follow soon after it came out more than a year ago. It's focus is on the very ramifications you speak of... in this case, something as seemingly...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 24, 2024 at 3:52 am
Heh... New tag line... SQL Server 2022... It just runs slower... A LOT SLOWER!
--Jeff Moden
Change is inevitable... Change for the better is not.
July 22, 2024 at 9:28 pm
After long hours, days and weeks the system back to healthy state. The biggest problem was bad developers code that had to be changed. That was...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2024 at 7:49 pm
That is really awesome, Jeff! In fact, that's outstanding. In my environment we do unit testing and UAT, and that's about it. We don't have the success rate that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2024 at 3:38 am
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2024 at 5:59 am
Hmmm, Jeff going. I'm going to have to see if I can make it.
Ed Wagner and I will be arriving in the afternoon on that Friday. Man, I understand...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2024 at 5:00 am
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2024 at 4:36 am
Install this TVF.
Then this SQL will do the job
select x.value value1, x.value+1000001 value2
from dbo.GENERATE_SERIES(-999999999,+999999999,1) x
;
Install this TVF.
Then...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2024 at 4:33 am
After long hours, days and weeks the system back to healthy state. The biggest problem was bad developers code that had to be changed. That was killing the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2024 at 4:24 am
I guess our code coverage is 500% plus a post prod kicker...
DEV
QA
DEVREVIEW (DBA Review and regression checks)
STAGE (UAT)
PREPROD (UAT and full system checks on full size from nightly restores which...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 18, 2024 at 4:19 am
2nd page bump to get post to appear
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2024 at 4:41 am
-- Create TableA CREATE TABLE TableA ( MainID INT, JoiningID INT );
-- Insert data into TableA INSERT INTO TableB (MainID, JoiningID) VALUES
(No column name)
...
Heh... you didn't try to run...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2024 at 4:36 am
Attached is some sample data. I could get this code to work, by inserting one row where FY/YEAR is 2024 and all of FY/YEAR 2025.
The original tables data goes...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2024 at 4:30 am
I'd rather go for a nice dinner and maybe some pool shooting at a good bar with big screens to watch the lions game than to get caught up in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2024 at 3:41 am
Viewing 15 posts - 451 through 465 (of 59,063 total)