Home >> FAQs/Tutorials >> SQL Server FAQ

SQL Server FAQ - Time-Only Date and Time Literals

By: FYIcenter.com

(Continued from previous topic...)

What Happens If Time-Only Values Are Provided as Date and Time Literals?

If only time value is provided in a data and time literal, the SQL Server will pad the date value with a zero, representing the base date, January 1, 1900. The tutorial exercise below gives you some good examples:

-- 'hh:mi:ss.mmm' format
DECLARE @x DATETIME;
SET @x = '22:55:07.233';
SELECT @x;
GO
1900-01-01 22:55:07.233

-- 'hh:mi:ss.mmmAM/PM' format
DECLARE @x DATETIME;
SET @x = '10:55:07.233PM';
SELECT @x;
GO
1900-01-01 22:55:07.233

-- 'hh:miAM/PM' format
DECLARE @x DATETIME;
SET @x = '10:55PM';
SELECT @x;
GO
1900-01-01 22:55:00.000

1. What Is a Constant or Literal?
2. How To Write Character String Constants or Literals?
3. What Is a Collation?
4. How To Specify the Collation for a Character Data Type?
5. What Happens If Strings Are Casted into Wrong Code Pages?
6. How To Find Out What Is the Default Collation in a Database?
7. How Fixed Length Strings Are Truncated and Padded?
8. How To Enter Unicode Character String Literals?
9. How To Enter Binary String Literals?
10. How To Enter Date and Time Literals?
11. Why I Can Not Enter 0.001 Second in Date and Time Literals?
12. What Happens If Date-Only Values Are Provided as Date and Time Literals?
13. What Happens If Time-Only Values Are Provided as Date and Time Literals?
14. What Are Out-of-Range Errors with Date and Time Literals?
15. What Happens If an Integer Is Too Big for INT Date Type?
16. How Extra Digits Are Handled with NUMERIC Data Type Literals?
17. How REAL and FLOAT Literal Values Are Rounded?
18. What Are the Underflow and Overflow Behaviors on FLOAT Literals?