Thumbs up for YYYY-MM-DD, removes needless confusion caused by regional formats of MMDD... or DDMM....

2025-09-06

Essentially Microsoft indicated it works as designed, and it was my fault for wrapping my call to sp_dropserver in TRY...CATCH. If I had not done so, the internal check of...

Tried working through Microsoft support and finally "accepted" them archiving it, basically "works as designed". Apparently, it is my fault for using TRY...CATCH and catching the error they were going...

Found that different behavior (2019) was "illusion". We had older version of our software on 2019, which still had a "fix" that was somehow deleted from current version. The fix...

Will notify when there are results from Micrsoft support request.

Did check, and @@TRANCOUNT is zero just after TRY, then one just after CATCH. Seems to be "leaking" out of stored...

Nope, no implicit transactions (one of things I checked). Once I figure out my Micrsoft support options, I'll follow up with them. Just thought I'd share this in case anyone...

Fascinating discussions, but what was "wrong" with my solution? I heard stuff like it is not usable except on SQL 2022, but this IS the SQL 2022 forum, is it...

Just got answer:

This is a known issue. Microsoft has said that this will be fixed in CU1 for SQL 2022. The fix is also available in the RTM version of...

Why not just use OUTPUT INTO clause of the UPDATE?

SET NOCOUNT ON
;
DECLARE @TMP
TABLE 
(
serialnumber
VARCHAR (500)
)
;
INSERT INTO
@TMP 
VALUES
('1232132|2343345435|34543534534534|3344562534')
,
('23243|23423432432|34543534534235|3344562534')
;
SELECT
Parsed.value
FROM
(
SELECT
*
FROM
@TMP
CROSS APPLY
string_split (serialnumber, '|', 1)
)
AS
Parsed
INNER JOIN 
(
SELECT
serialnumber
,
MAX (ordinal)
AS
MaxOrdinal
FROM
@TMP
CROSS APPLY
string_split (serialnumber, '|', 1)
GROUP BY
serialnumber
)
AS
EntryCount
ON
Parsed.serialnumber = EntryCount.serialnumber
AND
Parsed.ordinal = MaxOrdinal - 1
;

Have PowerShell script that repeatedly invokes SQLCMD. Of the hundreds of invocations, a random handful will fail with this error on every invocation of the script. The script is run...

Current size on E: drive is shown as 2.02 TB, size to restore on E: is 2.66 TB. Thus you need 0.64 TB of free space on E: (in addition...

Yup, all our fault. The trigger ti_Restart_Job was added by the team to handle restarting jobs that are hung, but was not implemented very well. Thanks for help finding the...

Grant,

Great references! I had to do a double take after reading your article and then finding my 4 health logs covered the last two seconds! I am diving deeper now,...

Grant,

Thanks for suggestions. I will reply later with whatever I discover.