This article explores the main differences between the datetime and smalldatetime data types in SQL Server.
Both data types are used for storing date and time values, however, there are differences between the two. In most cases you’re better off avoiding both types and using datetime2 instead (Microsoft also recommends this). In any case, here’s a comparison of these two data types.
This article explores the main differences between the datetime2 and smalldatetime data types in SQL Server.
Both data types are used for storing date and time values, however, there are some important differences between the two. In most cases you’re better off using datetime2 (Microsoft also recommends this), however there might be some scenarios where you need to use smalldatetime.
This article explores the main differences between the datetime and datetime2 data types in SQL Server.
If you’re not sure which one to use, use datetime2 (see its advantages below).
In this article I look at the storage size of the time data type in SQL Server.
In particular, I look at the following:
DATALENGTH()DATALENGTH() after converting to varbinaryCOL_LENGTH()DBCC PAGE()In this article I look at how the datetimeoffset data type is stored in SQL Server, and how you can get different reported storage size results, depending on what you’re doing with it.
This is similar to what I did with the datetime2 data type.
In particular, I look at the following:
DATALENGTH()DATALENGTH() after converting to varbinaryCOL_LENGTH()DBCC PAGE()In this article I share some observations I’ve had regarding the datetime2 data type’s storage size in SQL Server. Perhaps I will clarify some points about the actual storage size used by this data type when stored in a database.
In particular, I look at the following:
DATALENGTH()DATALENGTH() after converting to varbinaryCOL_LENGTH()DBCC PAGE()Some of those seem to contradict each other, and you will see two different storage size amounts for the same value, depending on where you look.
This article provides a side-by-side comparison of the date and time data types in SQL Server regarding their range, accuracy, and storage size.
When you convert between date and time data types in SQL Server, you need to be mindful of how the new data type will handle the value you’re trying to assign to it.
In some cases you might lose part of the value, in other cases you might gain a bunch of zeros (increasing storage size in the process). You may also end up with a value that’s been rounded up.
The following articles contain examples of conversions between the different date and time data types, with a particular focus on the issues I just mentioned.
If you have a datetimeoffset value, but you don’t need the date and time zone offset part, converting it to time will save you a lot of storage space (while removing unnecessary details from the value). This article contains examples of converting a datetimeoffset value to a time value in SQL Server.
If you have a datetimeoffset value, but you don’t need the time and time zone offset part, converting it to date will save you a lot of storage space (while removing unnecessary details from the value). This article contains examples of converting a datetimeoffset value to a date value in SQL Server.