In SQL Server 2008 a new datatype will be introduced that can support storing of date values from the year 0001 to 9999. This new datatype is called datetime2.
OK, so tell me what's wrong with the following picture:
- smallint, int, bigint
- smalldatetime, datetime, datetime2
These are all datatypes in SQL Server 2008. Why on earth have they called this new one datetime2? Surely bigdatetime would be more consistent.
I do worry about the thought processes that go on in building 35 sometimes. Expect a synonymn to appear for datetime2 in SQL Server 201X.