Comments on: SQL SERVER – Precision of SMALLDATETIME – A 1 Minute Precision

By: Akram

Akram — Tue, 19 Jun 2012 08:51:35 +0000

Very Nice Article
I tested this query and i analyse that precision of smalldatetime is forwarded 1minute after 30second of actual time,Here is the script run together…

declare @test datetime2
set @test=GETDATE()
print @test

declare @test1 smalldatetime
set @test1=GETDATE()
print @test1

declare @test2 datetime
set @test2=GETDATE()
print @test2

By: madhivanan

madhivanan — Mon, 18 Jun 2012 06:21:28 +0000

Here is an example

declare @d datetime
select @d=’20010101 12:19:44′
select dateadd(minute,datediff(minute,0,@d),0)

By: Jone

Jone — Sun, 17 Jun 2012 06:14:25 +0000

Hello
how can i cut seconds from datetime, without rounding the minute?
i want the minutes to stay, but cut the seconds from date

By: SQL SERVER – SmallDateTime and Precision – A Continuous Confusion « SQL Server Journey with SQL Authority

Tue, 22 May 2012 01:31:45 +0000

[...] Now if you do not want to continue reading blog post head over my previous blog post over here: SQL SERVER – Precision of SMALLDATETIME. [...]

By: SQLAuthority News – A Monthly Round Up of SQLAuthority Blog Posts Journey to SQL Authority with Pinal Dave

Wed, 30 Jun 2010 01:31:07 +0000

[...] month started very interesting subject of SQL SERVER – Precision of SMALLDATETIME – A 1 Minute Precision which lead to few datetime related blog posts. I find them very interesting and hopefully you will [...]

By: Eric Russell

Eric Russell — Mon, 07 Jun 2010 14:20:42 +0000

I’ve always defaulted to using the 4 byte smalldatetime instead of the 8 byte datetime, unless there is a business requirement or technical reason to store sec and ms. However, one pitfall to using smalldatetime is if one includes it as part of a unique key, or attempts to sort using the column, and doesn’t consider that multiple records inserted within approx minute will result in duplicate date/time values.
For example in a point of sale system, a key based on cash register ID and transaction smalldatetime may pass through QA and work in production without collision for weeks or months under normal circumstances, but then fail if a transaction is cancelled and a new transaction is immediately started. Also, I’ve seen circumstances where it was expected that transactions, perhaps line items on an invoice, would be sorted based on the order they were inserted, but the insert_date column was insufficient due to it not having sec or ms resolution.

By: Nutan

Nutan — Tue, 01 Jun 2010 10:15:16 +0000

Sir,
I’ve used this datatype so many times but i’ve not noticed the issue yet. Thanks for posting this issue…..

By: Adnan Badar

Adnan Badar — Tue, 01 Jun 2010 08:01:08 +0000

Nice article,

Just want to be more accurate about rounding,
example

DECLARE @varSDate AS SMALLDATETIME
SET @varSDate = ’1900-01-01 12:12:29.998′
SELECT @varSDate C_SDT
– Will give you ’1900-01-01 12:12:00′
SET @varSDate = ’1900-01-01 12:12:29.999′
SELECT @varSDate C_SDT
– Will give you ’1900-01-01 12:13:00′