Press "Enter" to skip to content

Day: October 19, 2026

Skipping Incompatible Objects in Bacpac Restoration

Erik Ejlskov Jensen shares some good news:

If you have ever tried to export a SQL Server database to a .bacpac file with sqlpackage, you have most likely run into the dreaded SQL71627 error, complaining about a Windows user or login. I ran into it myself a few years ago, and the only workaround was to drop the offending users from the database (or a copy of it) before running the export.

With sqlpackage 170.6.28-preview, that workaround is no longer needed. The Export action has two new properties that let you remove objects that are not compatible with Azure SQL Database while exporting, and write a report of what was removed.

Click through for a demonstration.

Leave a Comment

What’s the Time Again?

Umachandar Jayachandran checks a watch:

Affected locations in British Columbia, Alberta, and Manitoba will not turn their clocks back at 02:00 local time on November 1, 2026. They will remain at UTC−07:00, UTC−06:00, and UTC−05:00, respectively. 

Microsoft’s interim guidance for British Columbia, Alberta, and Manitoba describes the new Windows time zones and temporary workarounds. 

SQL Server on Windows requires the applicable Windows update—not a separate SQL Server product update. For SQL Server on Linux, Azure SQL Database, and Azure SQL Managed Instance, the following guidance applies when the new regional time zones are not yet available in your deployment. 

Click through if you have anything in that latter bucket.

Leave a Comment

Disabling FileStream and FileTable on a SQL Server Instance

Stephane Haby turns off a feature:

A customer recently asked me to disable FileTable/FileStream on their instance because the databases no longer use it, and to ensure that this is indeed the case.
The aim is to migrate to a new architecture without FileTable/FileStream in a second time.

The tricky bit is that the relevant database is also inside of an Availability Group. Click through for the process.

Leave a Comment

Comparing JSONB to hstore in Postgres

Hubert Lubaczewski re-creates an issue:

Some time ago I read this blogpost.

They wrote about logging changes to table using a trigger, but one thing that caught my attention was:

Storing only the changed columns made the log five times smaller and the trigger slower.

Figured I can try it myself…

Unfortunately they didn’t provide schema of table, nor test updates. So, let’s make test case:

Click through for the demo, and how a change from JSONB to hstore for changed data improved performance a fair bit.

Leave a Comment

Rebuilding pgbuild

Dave Page digs into a repo:

My job at pgEdge allows me a significant amount of time to work on pgAdmin, a project I started nearly 30 years ago. The previous blog and this followup is an update on some of the recent work I’ve been doing.

In my last post I wrote about moving pgAdmin’s build farm from Jenkins to GitHub Actions, and I promised a follow-up about pgbuild, which is the least famous repository in the pgAdmin organisation and quietly one of the most important. If you have installed pgAdmin on Windows in the last year or so, or on macOS since the move to GitHub Actions, you ran code that came from the buildfarm.

Click through to learn more about this base repository, as well as one significant problem they fixed.

Leave a Comment