Cody Konior
@codykonior.bsky.social
Expert at scaling SQL Server and PowerShell. Happily married with 4 cat children 😻
Just saying because it’s yet another adult thing that seems super simple on the surface but has depths of craziness that normal people shouldn’t have to know about 💀
July 8, 2025 at 7:24 AM
Just saying because it’s yet another adult thing that seems super simple on the surface but has depths of craziness that normal people shouldn’t have to know about 💀
Side thing but I’m on the mailing list of a local arborist and he sent a long article a week ago about this.
How there’s all kinds of rules over who pays based on whether the tree is native, and power companies don’t follow their own rules, and he has to answer angry confused calls all the time.
How there’s all kinds of rules over who pays based on whether the tree is native, and power companies don’t follow their own rules, and he has to answer angry confused calls all the time.
July 8, 2025 at 7:23 AM
Side thing but I’m on the mailing list of a local arborist and he sent a long article a week ago about this.
How there’s all kinds of rules over who pays based on whether the tree is native, and power companies don’t follow their own rules, and he has to answer angry confused calls all the time.
How there’s all kinds of rules over who pays based on whether the tree is native, and power companies don’t follow their own rules, and he has to answer angry confused calls all the time.
These are procedures like utility procedures, Hallengren stuff, etc that isn’t part of your project but that does get put into each database usually by a seperate process.
May 24, 2025 at 11:56 AM
These are procedures like utility procedures, Hallengren stuff, etc that isn’t part of your project but that does get put into each database usually by a seperate process.
The other cool thing I found was; have procedures outside your project but that you don’t want dropped? You can just extract them into a dacpac and reference it. Now it won’t drop them on deploy anymore.
And yeah you can “turn off all drops” but often that’s not what you want.
And yeah you can “turn off all drops” but often that’s not what you want.
May 24, 2025 at 11:55 AM
The other cool thing I found was; have procedures outside your project but that you don’t want dropped? You can just extract them into a dacpac and reference it. Now it won’t drop them on deploy anymore.
And yeah you can “turn off all drops” but often that’s not what you want.
And yeah you can “turn off all drops” but often that’s not what you want.
Specifically last week you could OPENJSON a JSON variable. Now you can’t.
There’s a limitation listed in the documentation that you can convert to NVARCHAR first. But this was working functionality that has been changed overnight.
That’s what you get for using Preview features I guess 🤷♂️
There’s a limitation listed in the documentation that you can convert to NVARCHAR first. But this was working functionality that has been changed overnight.
That’s what you get for using Preview features I guess 🤷♂️
May 20, 2025 at 2:47 AM
Specifically last week you could OPENJSON a JSON variable. Now you can’t.
There’s a limitation listed in the documentation that you can convert to NVARCHAR first. But this was working functionality that has been changed overnight.
That’s what you get for using Preview features I guess 🤷♂️
There’s a limitation listed in the documentation that you can convert to NVARCHAR first. But this was working functionality that has been changed overnight.
That’s what you get for using Preview features I guess 🤷♂️
Yeah but this year they’re making it even thinner!!! 😏 /s
May 11, 2025 at 12:33 PM
Yeah but this year they’re making it even thinner!!! 😏 /s
Unfortunately though I have no avenue to support tickets in my current company.
Sucks to be me.
Sucks to be me.
May 6, 2025 at 4:36 PM
Unfortunately though I have no avenue to support tickets in my current company.
Sucks to be me.
Sucks to be me.