Part 3 of 6. The series: 1. The plan and the lab · 2. Check what is there · 3. Export what the target needs (this post) · 4. Back up and upload · 5. Restore · 6. Check post-migration, and clean up. Part 2 ended with a VM that passed all ten gates: it … Continue reading AdventureWorks2025 to an Azure SQL VM, part 3: export what the target needs
AdventureWorks2025 to an Azure SQL VM, part 2: check what is there
Part 2 of 6. The series: 1. The plan and the lab · 2. Check what is there (this post) · 3. Export what the target needs · 4. Back up and upload · 5. Restore · 6. Check post-migration, and clean up. Part 1 ended with a VM in Azure, a storage account, a … Continue reading AdventureWorks2025 to an Azure SQL VM, part 2: check what is there
AdventureWorks2025 to an Azure SQL VM, part 1: the plan and the lab
Part 1 of 6. The series: 1. The plan and the lab (this post) · 2. Check what is there · 3. Export what the target needs · 4. Back up and upload · 5. Restore · 6. Check post-migration, and clean up. A week ago I wrote about site-to-site migration and rollback: the method, … Continue reading AdventureWorks2025 to an Azure SQL VM, part 1: the plan and the lab
Site-to-site migration and rollback
First things first: Hugo, one of the best humans to have walked the face of the Earth passed away. You can read about his last moments here: https://sqlserverfast.com/blog/hugo/2026/11/final-post/. I, for once, am lost for words.Go grab his video trainings (basically for free for the depth of knowledge you will get), that is the least we … Continue reading Site-to-site migration and rollback
Using Performance Monitor Lite with Local LLMs
The one and only Erik Darling (homepage) is doing his best to help us to make our lives easier by providing a fully fledged monitoring solution (two, actually) for SQL Server, all this for free. Yes, FREE: https://github.com/erikdarlingdata/performancemonitor. Due to the nature of my job I can only use the Lite version, not the fully … Continue reading Using Performance Monitor Lite with Local LLMs
FOR XML PATH, STRING_AGG and AI
For the AI warriors out there - I was rewriting a bunch of stored procedures (270+, to be more precise), so naturally AI comes into play (QWEN Coder Next 80B at 8 bit and GPT-OSS 120B MXFP4 - not as precise, but works good enough. Yes, I need to work with local models because of … Continue reading FOR XML PATH, STRING_AGG and AI
Find and Change (N)VARCHAR(MAX) to (N)VARCHAR(XXX)
I know, I know, everything I do is rushed and not properly explained, apologies for that. Anyway.During some investigation, I came across some badly designed tables where most of the columns meant to hold character data were NVARCHAR(MAX), all this while the maximum length of the strings were something in the area of 30-50 characters. … Continue reading Find and Change (N)VARCHAR(MAX) to (N)VARCHAR(XXX)
Script to update the dates on AdventureWorks database
In case you ever needed this: IF OBJECT_ID('tempdb..#GeneratedScripts') IS NOT NULL DROP TABLE #GeneratedScripts; CREATE TABLE #GeneratedScripts (Id INT IDENTITY(1,1), SqlScript NVARCHAR(MAX)); -- 1. Setup global ceiling INSERT INTO #GeneratedScripts (SqlScript) VALUES ('DECLARE @TargetCeiling DATETIME = GETDATE();'); DECLARE @SchemaName NVARCHAR(256), @TableName NVARCHAR(256), @AnchorColumn NVARCHAR(256); DECLARE @Sql NVARCHAR(MAX), @ColumnUpdates NVARCHAR(MAX); DECLARE tbl_cursor CURSOR FOR SELECT DISTINCT … Continue reading Script to update the dates on AdventureWorks database
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database – when migrating SSRS databases to a new server
You have restored your databases, you renamed them if needed (in my case ReportServer and ReportServerTempDB from ReportServer$Instance and ReportServer$InstanceTempDB), jobs, everything, when migrating SSRS to a new server. Yet, scheduled subscriptions still not working (oddly enough, ad-hoc ones were working, could browse reports, etc.). In my case, when I tried editing Subscriptions, I hit … Continue reading An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database – when migrating SSRS databases to a new server
Wierd tuning trick with dynamic SQL when encountering unmatched indexes
Later edit: Both Uwe Ricken (https://www.linkedin.com/in/uwericken/, https://www.db-berater.de/) and Sascha Lorenz (https://www.linkedin.com/in/saschalorenz/) correctly pointed out that my little inconsisted writing was a tad too inconsistent - first of all, the title itself was NOT highlighting the very point of this blog post: unmatched indexes and how to deal with them by using dynamic SQL. Truth be … Continue reading Wierd tuning trick with dynamic SQL when encountering unmatched indexes