SQL 2008 introduced a bunch of new features, some of which I took annoyance at - the naming for all the different types of new date / time datatypes. (And I thought that varchar(MAX) was a poor name choice too - why not just make TEXT become that? or if a new type was needed why not LONG VARCHAR?)
Anyways, what things in SQL2008 have you gone back and changed old code to take advantage of, or changing your coding style for new code
EDIT Squirrel asked: "It is not broken why change?"
For me the reasons would be
but also I might change the way we write CRUD routines if there where enhancements that improved them (MERGE might be one); changing our templates for these would mean that new routines used the new style, and over time old routines would be refactored (for us that would be whenever a change was needed to that routine, or if there was a benefit in the new template that we specifically wanted to apply to certain tables)
Here's what I love -- you can finally assign default values in a declare statement!
As far as I can tell, this is new in 2008. And I love it. About time!
answered Oct 07 '09 at 03:46 PM
Jeff Smith ♦
I'm now using merge a lot - never thought I would. Use date and time datatypes to save space but not sure it's such a good idea as it needs a convert to use for some date functions.
Had to use ssis instead of bulk insert/bcp to import utf-8 data - not sure whether that stopped working in 2005 or 2008 though.
Started using reporting services more as it seems to work in 2008.
answered Oct 07 '09 at 02:45 PM
T-SQL wise there's no need to change anything. IMO the single best T-SQL upgrade is the MERGE statement. It allows for some really powerful conditional table manipulation all in one statement. It also lessens the number of locks taken during the so called UPSERT that the previous if exists update else insert method.
answered Oct 07 '09 at 09:51 AM
One of my favorite new features of SQL Server 2008 is composable DML.
answered Oct 07 '09 at 04:23 PM