External Article

The DIS-Information Principle: A Splitting Headache

You can easily re-factor bad DML code, but if a database design is wrong, you can do little to rescue the problem, even with expert queries. So what constitutes 'wrong RDBMS design? What are these errors that continually crop up? How can you recognise them and fix them? Joe embarks on a new series of articles by identifying a series of bad practices based on the habit of 'splitting' that which shouldn't be split.

Blogs

The 2026 Redgate Summit in New York City

By

We’re coming back to New York, which is exciting for me. I love NYC....

Monitoring Fabric Mirroring for SQL 2025

By

I previously wrote about how the underlying technology for Fabric mirroring changed with SQL...

Monday Monitor Tips: Intelligent Alert Thresholds

By

At the recent Redgate Summit in Chicago, I demo’d (lightly) the ML based Alert...

Read the latest Blogs

Forums

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Seeding a Fabric Warehouse with dbt for Visual Studio Code: The Fabric Modern Data Platform

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Seeding a Fabric Warehouse with...

Doing the Little Things

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Doing the Little Things

Visit the forum

Question of the Day

Historical Data Tracking

If I want to track historical data values, which mechanism should I use?

See possible answers