Comments for SQL from the Trenches

Comment on Replication: Snapshot Agent fails on date conversion by Davide Pozzi

Davide Pozzi — Mon, 23 Jan 2023 12:15:29 +0000

Excellent analysis and a lot of time saved, great! Thank you.

Comment on Setting up replication from on-premise SQL Server to Azure SQL DB by Pactain

Pactain — Mon, 26 Sep 2022 15:21:23 +0000

Hello from 2022!

Great tutorial, still works, saved my bacon today. You don’t need .secure. part if you’re running VM on already on Azure

Comment on Geometry vs Geography by 7 Spatial Databases for Your Enterprise (in 2021) - John Jason Fallows

7 Spatial Databases for Your Enterprise (in 2021) - John Jason Fallows — Thu, 25 Nov 2021 17:33:11 +0000

[…] important to note that SQL Server supports two spatial data types (geometry and geography). Why have two data types? The geometry data type represents data in Euclidean coordinates. Whereas, the geography data type […]

Comment on Easy pivot: From key-value pairs to columns by Jim

Jim — Tue, 29 Jun 2021 22:37:54 +0000

Works great. Quick note: Select * works too. Column names only needed in the for clause.

Comment on Deadlock Detector: Drop it like it’s hot! by Shashi Bhosale

Shashi Bhosale — Sun, 28 Feb 2021 03:01:55 +0000

I am facing the same problem. I cant even find the uninstallation as the web site is down. Can somebody help. My email is [email protected]

Comment on Easy pivot: From key-value pairs to columns by Julian

Julian — Wed, 11 Nov 2020 10:21:49 +0000

Life saver, now i can consume table like structure in SSIS while making writing my database migration, instead of dealing with KVP on certain tables.

Comment on SSISDB: Why bigger isn’t always better by Raphael Ferreira

Raphael Ferreira — Fri, 15 May 2020 16:44:13 +0000

Pardon my ignorance: Why, instead of simply changing the retention from 365 days to, say 90, do you have to run the script? I’m sure there is something I am not seeing, but, I’m just not seeing it. Insights appreciated. Raphael

Comment on Avoid a big SSISDB by logging less…? by DevJef

DevJef — Fri, 15 May 2020 15:50:21 +0000

In reply to Raphael Ferreira.

Depends on your workload of course. But in general: yes!
My suggestion is: Leave it on default, keep an eye on it, and change if needed.
But in my case, keeping it on default ended up in a disaster 😉

Comment on Avoid a big SSISDB by logging less…? by Raphael Ferreira

Raphael Ferreira — Fri, 15 May 2020 15:31:47 +0000

Fascinating… Performance is slower than Basic… Ah, Microsoft..! You never cease to amaze me… Correct me if I am wrong, but it sounds to me that the only acceptable log level for day to day operation is a custom one, correct?

Comment on SSISDB: Why bigger isn’t always better by DevJef

DevJef — Fri, 15 May 2020 15:01:00 +0000

In reply to Raphael Ferreira.

You can, but because it’s so much data the data will never be cleaned. The cleanup job will time out.
So that’s why we did it like this.