External Article

How to Get SQL Server Dates and Times Horribly Wrong

One of the times that you need things to go right is when you are doing analysis and reporting. This is generally based on time and date. A sure-fire way of getting managers upset is to get the figures horribly wrong by messing up the way that you handle datetime values in SQL Server. In the interests of peace, harmony and a long career in BI, Robert Sheldon outlines some of the worst mistakes you can make when using SQL Server dates.

Blogs

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...

Optimizing Redshift Performance by Configuring WLM Queues

By

Efficient query performance in Amazon Redshift often comes down to how well you manage...

PowerShell Strikes Back: Return of the Loop

By

Welcome back to PowerShell Strikes Back. We’re three weeks in, and the training is...

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