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

I recommend Smart Brevity (book) for communications

By

Following the advice in Smart Brevity improves communication.

SQL Server 2025 Developer Edition – One size fits all

By

Microsoft has released SQL Server 2025, bringing big improvements to its main database engine....

Monday Monitor Tips: Learning While Using the Tool

By

A customer was asking about what certain items in Redgate Monitor mean. They have...

Read the latest Blogs

Forums

Switch partition: NULL boundary id

By vpolasa

I have table: t1 in schema1 with 19 billion records. I have another table...

Minimally Viable Security

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Minimally Viable Security

Encoding NULL

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Encoding NULL

Visit the forum

Question of the Day

Encoding NULL

What is returned from this code in SQL Server 2025?

SELECT BASE64_ENCODE(NULL)

See possible answers