Does resetting an Identity Seed to a specific value via DBCC CHECKIDENT(..., RESEED, new_seed_value) work the way the documentation states? It depends 🙃
Beware of big green dragons, er, well, of unexpected changes when changing a column's datatype. You might be unpleasantly surprised! 🙀 Beware!
Have you ever needed to prevent an entire script (or part of one) from executing? See how the session-level options PARSEONLY and NOEXEC can accomplish this.
For SQLCLR in SQL Server 2017 and newer, when "CLR strict security" is enabled, does PERMISSION_SET matter, or are assemblies always UNSAFE?
An in-depth analysis of the new native UTF-8 support in SQL Server 2019.
(last updated: 2019-01-10 @ 18:00 EST / 2019-01-10 @ 23:00 UTC ) With the additional (and annoying) configuration step required to get SQLCLR Assemblies to load starting in SQL Server 2017, some people have been wondering what is going on with SQLCLR. Considering that this new restriction is the only real change to SQLCLR since… Continue reading SQLCLR vs SQL Server 2017, Part 8: Is SQLCLR Deprecated in Favor of Python or R (sp_execute_external_script)?
Demystifying What "sqlservr -q" Actually Does (last updated: 2019-01-07 @ 02:25 EST / 2019-01-07 @ 07:45 UTC ) For various reasons, people sometimes find themselves in the unfortunate (and unenviable) situation of having an Instance of SQL Server configured with the wrong Collation. This can often lead to unexpected errors and/or sorting and comparison behavior.… Continue reading Changing the Collation of the Instance, the Databases, and All Columns in All User Databases: What Could Possibly Go Wrong?
Occassionally I want / need to change a Windows setting that is not configurable via Control Panel or Settings. For example: Enabling long-path support (long = paths over 259 characters) Disabling all Live Tiles The instructions usually require using Group Policy Editor (gpedit.msc). Unfortunately, I am using Microsoft Windows 10 Home Edition, and that does… Continue reading Enable Group Policy Editor (gpedit.msc) on Windows 10 Home Edition
The investigation into valid T-SQL identifier characters continues. Apparently I was not done.
If you have ever used SET CONTEXT_INFO to store a simple value, you probably ran into this frustrating behavior 🙀