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.

External Article

SQL Server User-Defined Functions

User-Defined Functions (UDFs) are an essential part of the database developers' armoury. They are extraordinarily versatile, but just because you can even use scalar UDFs in WHERE clauses, computed columns and check constraints doesn't mean that you should. Multi-statement UDFs come at a cost and it is good to understand all the restrictions and potential drawbacks. Phil Factor gives an overview of User-defined functions: their virtues, vices and their syntax.

Blogs

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

T-SQL Tuesday #200: When I Look at a Query …

By

This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...

Reflections on the Life of a DBA

By

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

Read the latest Blogs

Forums

A Quick Second Opinion

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Second Opinion

Five Intelligent Query Processing Features in SQL Server 2022 That Quietly Tune Your Workload

By vgupta

Comments posted to this topic are about the item Five Intelligent Query Processing Features...

Checking the Error Log I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking the Error Log I

Visit the forum

Question of the Day

Checking the Error Log I

On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?

See possible answers