External Article

The Basics of Good T-SQL Coding Style – Part 2: Defining Database Objects

Technical debt is a real problem in database development, where corners have been cut in the rush to keep to dates. The result may work but the problems are in the details: such things as inconsistent naming of objects, or of defining columns; sloppy use of data types, archaic syntax or obsolete system functions. With databases, technical debt is even harder to pay back. Robert Sheldon explains how and why you can get it right first time instead.

Blogs

The Book of Redgate: Hours

By

I have said and written this many times: Redgate Software is the type of...

How to Check TDE Progress and Elapsed Time in SQL Server

By

How to Check TDE Progress and Elapsed Time in SQL Server ...

PostgreSQL Support in the Data API Builder

By

Next week I’m at VS Live in San Diego (register and join me) and...

Read the latest Blogs

Forums

Squared Values

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Squared Values

I Don't Want To Do XX

By Steve Jones - SSC Editor

Comments posted to this topic are about the item I Don't Want To Do...

Managing Feature Flags with GET_BIT() and SET_BIT() in SQL Server

By john.martin

Comments posted to this topic are about the item Managing Feature Flags with GET_BIT()...

Visit the forum

Question of the Day

Squared Values

What happens when I run this code in SQL Server 2022?

SELECT SQUARE('12')

See possible answers