External Article

Yet Another SQL Strategy for Versioned Data

There is a popular design for a database that requires a built-in audit-trail of amendments and additions, where data is never deleted, but superseded by a later version. Whilst this is conceptually simple, it has always made reporting the latest version of data complicated. Alex Kuznetsov joins the debate on the best way of doing this with an example using an indexed view and the filtered index.

Blogs

QUOTENAME Basics: #SQLNewBlogger

By

Recently I ran across some code that used a lot of QUOTENAME() calls. A...

When growing companies outgrow Excel

By

There are some telltale signs that your growing business has outgrown Excel for your...

T-SQL Tuesday #198 Roundup: How Do You Detect Data Changes?

By

Thank you to everyone who participated in T-SQL Tuesday #198! When I wrote the...

Read the latest Blogs

Forums

Stairway to Reliable Database Deployment Level 3 – Rehearsing Changesets Across Environments

By Massimo Preitano

Comments posted to this topic are about the item Stairway to Reliable Database Deployment...

QUOTENAME Quote Parameters

By Steve Jones - SSC Editor

Comments posted to this topic are about the item QUOTENAME Quote Parameters

Limit the Blast Radius

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Limit the Blast Radius

Visit the forum

Question of the Day

QUOTENAME Quote Parameters

When I use QUOTENAME(), I can optionally provide the character used to surround the string in the result. Can I use any character?

See possible answers