Press "Enter" to skip to content

Day: July 2, 2026

Building a Lakehouse Table Health Pipeline

Published 2026-07-02 by Kevin Feasel

Gilbert Quevauvilliers builds a pipeline:

In this post I will show how I used GitHub Copilot CLI / Agent mode in VS Code to create a Microsoft Fabric pipeline that checks Lakehouse table health and only optimizes tables that require maintenance. I’ll also show the prompts I used, the issues I ran into, and how Copilot helped me resolve them.

Recently Microsoft announced Lakehouse table health. The post showed how you can check can check the health of your Lakehouse table in a very simple way.

Read on to see what this feature can do, as well as how Gilbert was able to gin up (with the help of GitHub Copilot) a pipeline to optimize lakehouse tables. What I appreciate is that Gilbert also included the errors in the process, rather than making it seem like everything with perfectly the first time around.

Leave a Comment

SSMS Tools in VS Code

Published 2026-07-02 by Kevin Feasel

Denny Cherry has a new VS Code extension:

Are you a user of VS Code, but you wish that the MSSQL extension had more of the SQL Server Management Studio features? Good news, there’s now a VS Code Plugin that gives you those capabilities in VS Code by using the “SSMS Tools for SQL Server” extension.

Click through to see what it includes. There’s a pretty decent amount of existing SSMS functionality in this extension, especially on the database administrator side, where Azure Data Studio and VSCode historically have not focused.

Leave a Comment

Error 1408 with Availability Group Automatic Seeding

Published 2026-07-02 by Kevin Feasel

Sean Gallardy troubleshoots an error:

This used to be a very hot topic around SQL Server 2016 when automatic seeding first came out, then everyone learned how automatic seeding was just manual seeding but done for you and the topic went away. A decade later, it’s somehow back to being a hot topic. I guess all that is old is new again.

Error 1408 states that the database doesn’t have enough log to find a starting point with the primary/principal – which, let’s just use AG terminology from this point on because mirroring has been dead for 14 years and counting.

Mirroring has been dead and yet it lives on in undead form. Regardless of that, Sean provides some good information around what automatic seeding actually means and what you can do if you get stuck with Error 1408.

Leave a Comment

An Introduction to Spindle

Published 2026-07-02 by Kevin Feasel

Jonathan Stewart has an open-source tool:

A client wanted to see a feature that I had previously built for another customer. I obviously couldn’t just use real client data. When I used Faker and other tools like that, I got data that looked fine on its own but fell apart when I needed relational integrity such as needing an order to point to a customer which points to an address. AdventureWorks, Contoso, WideWorldImporters and the like are great for what they are, but they are either too small, too clean or not relevant to the demo.

I needed data that would not only look the part for the subject, but also follow relationships, have proper distributions, and so on.

So I built Spindle.

I’ve used Spindle for work purposes. It’s a good product for generating artificial data, either from one of the default data domains (e.g., HR, insurance, health care, manufacturing) or based on an existing database schema.

Leave a Comment

Too Many Tables and PostgreSQL

Published 2026-07-02 by Kevin Feasel

Laurenz Albe uncovers an oddity:

Recently, I helped a customer investigate database problems. It turned out that these problems could be traced back to too many tables in the database. Since this may come as a surprise to many users, I thought it worth the while to write about it.

Click through to see what was happening, as well as a demonstration of the problem. Granted, when you start talking about tens of thousands of tables, something has gone catastrophically wrong in your database architecture.

Leave a Comment