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

Houston AI-Lytics 2026–Powerpoint Slides

By

Thanks to everyone for attending my session on running a Local LLM. If you...

The Book of Redgate: Do the Right Things

By

I do believe that Redgate has been very customer focused since it’s inception. I’ve...

GenAI vs Dashboards: Not the Same (And Never Will Be)

By

There’s a question I’ve been hearing more and more lately, especially as Copilot, Fabric,...

Read the latest Blogs

Forums

T-SQL in SQL Server 2025: JSON_ARRAYAGG

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Spring Connections and Learning at PASS On Tour

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spring Connections and Learning at...

Multiple Sequence Values

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Sequence Values

Visit the forum

Question of the Day

Multiple Sequence Values

How do I easily get the next 12 sequence values from a sequence object?

See possible answers