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

Reflections on the Life of a DBA

By

The DBA life is fraught with pain. Those battles that we endure are mostly...

Moving On-Prem PostgreSQL to the Cloud: Picking the Right Path for Big Tables

By

Every PostgreSQL migration eventually hits the same fork in the road. The database is...

A Spread of Vacation

By

I’m off on vacation today. Which is a little weird as I just got...

Read the latest Blogs

Forums

Inquiry – Enforcing ApplicationIntent=ReadOnly via GPO

By abdalah.mehdoini

Hello, I would like to ask whether it is technically possible to redirect a...

Calculating Geometric Mean in Power BI

By Dinesh Asanka

Comments posted to this topic are about the item Calculating Geometric Mean in Power...

TempDB Facts I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item TempDB Facts I

Visit the forum

Question of the Day

TempDB Facts I

Can I set Accelerated Database Recovery on tempdb?

See possible answers