External Article

The Basics of Good T-SQL Coding Style – Part 4: Performance

There are several obvious problems with poor SQL Coding habits. It can make code difficult to maintain, or can confuse your team colleagues. It can make refactoring a chore or make testing difficult. The most serious problem is poor performance. You can write SQL that looks beautiful but performs sluggishly, or interferes with other threads. A busy database developer adopts good habits so as to avoid staring at execution plans. Rob Sheldon gives some examples.

External Article

Data in Motion and Data at Rest

Microsoft (StreamInsight), and Azure Stream Analytics represent a very different model for processing data. They are concerned with processing complex event streams of data (CEPs) from such things as sensors to deduce significant patterns and apply filters. Joe Celko discusses the background to an intriguing technology of complex event processing to establish the difference between data at rest, and data on the move.

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