Technical Article

Mo-SQL

If you’re involved in the database world it’s hard to have missed the rise of the “no-sql” database products, designed to – depending on your view or the product I suppose – make databases simpler, break out of the transaction database paradigm, scale out across hundreds of machines, make it easy to change the db design (or not require one). I think some of the problems no-sql tries to solve are real, others reflect a lack of awareness/training/tools on how and why relational databases could not just solve the problem, but solve it better.

Blogs

Five Ways Redshift Serverless Quietly Eats Your Budget

By

It is Friday, the queries are running, and nobody is watching the bill. That...

A Career of Memories

By

Annabel retired from Redgate Software this week. Across most of my career at Redgate,...

Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead

By

As a SQL Server DBA with years of experience tuning production environments, I’ve seen...

Read the latest Blogs

Forums

Changes, Happiness, and a Few Tears

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changes, Happiness, and a Few...

BCP on Linux

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BCP on Linux

You Probably Don't Need a Vector Database

By Kumar Abhishek

Comments posted to this topic are about the item You Probably Don't Need a...

Visit the forum

Question of the Day

BCP on Linux

When running bcp on Linux, what is the field terminator?

See possible answers