July 1, 2009 at 12:56 am
Date is one of the most requested data types and finally MS implemented it in SQL Server 2008 and i love it. The new datatypes are just one of the greate improvements in SQL Server 2008!
If you havent upgraded yet I will give you some arguments:
🙂 Data compression, I shrinked one of our database with 75%, without performance loss (4 x Quad processor can handle the increased CPU usage.
🙂 Filtered indexes, I added more (covering) indexes to improve read performance in some of the queries without any or very little loss of write performance.
🙂 User defined Table type, and the possibility to pass the table between stored procedurs ( instead of temporary tables )
🙂 Multiple value inserts within a single INSERT statement
🙂 Auditing
This is just a subset of new features that i already have implemented and i think makes it worth the effort to consider upgrading.
/Håkan Winther
/Håkan Winther
MCITP:Database Developer 2008
MCTS: SQL Server 2008, Implementation and Maintenance
MCSE: Data Platform
July 1, 2009 at 4:43 am
Got me... I didn't read the question properly. Very good 😛
July 1, 2009 at 6:52 am
hakan.winther (7/1/2009)
Date is one of the most requested data types and finally MS implemented it in SQL Server 2008 and i love it. The new datatypes are just one of the greate improvements in SQL Server 2008!
I agree completely. It's so nice to be able to have a date without having to be concerned about the time.
July 1, 2009 at 8:28 am
That question has one major flaw - it does not take UDTs into consideration.
I could declare a data type DATE as CHAR(5) and then the correct answer would be '09/09'
How about that?
---------------------------------------------
[font="Verdana"]Nothing is impossible.
It is just a matter of time and money.[/font]
July 1, 2009 at 6:46 pm
I've just executed it on my SQL 2005 and it returns a result of 2008-10-09 00:00:00.
How strange is it (or not)?
Simon Liew
Microsoft Certified Master: SQL Server 2008
July 2, 2009 at 12:32 am
I didn't see on which version of SQL Server belongs this question, I concentrate on the code and sure that miss the correct answer couz in declaration of the variable I thought that we are discussing for the SQL Server 2008!
:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P:-P
July 2, 2009 at 5:59 am
Andeavour (7/1/2009)
Got me... I didn't read the question properly. Very good 😛
Me neither. D'oh! 😛
July 2, 2009 at 6:29 am
skjoldtc (7/1/2009)
hakan.winther (7/1/2009)
Date is one of the most requested data types and finally MS implemented it in SQL Server 2008 and i love it. The new datatypes are just one of the greate improvements in SQL Server 2008!I agree completely. It's so nice to be able to have a date without having to be concerned about the time.
It is a shame that Microsoft didnt implement Date a long time ago.
/Håkan Winther
MCITP:Database Developer 2008
MCTS: SQL Server 2008, Implementation and Maintenance
MCSE: Data Platform
July 2, 2009 at 7:01 am
Ok! Now we have choice to separate date from time declaring them as independent data types, but must have some care during development level that the date to be or not to be connected with the time!? - I think this was the problem why MS leave them together and on the other hand they added some functions detail to retrieve just time or date!
I don't know the exact reason, but now developers must be very smart how to connect date with time inside that date!!!
July 6, 2009 at 7:11 am
you got me!
July 7, 2009 at 6:17 am
Ha! I got it right but for the wrong reason. Didn't know there was a date datatype so i figured it would throw an error. lol.
November 24, 2009 at 12:07 am
DATE data type is of great help. I still remember that days when we had to use DATETIME data type for date and the time part was appended to it, even if we don't need it.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply