July 27, 2019 at 1:00 am
Comments posted to this topic are about the item SQL Server 2019 CTP 3.2 Available
July 27, 2019 at 11:06 am
I guess sometimes it comes down to whom it is more important to keep up to date, your employer or yourself.
Rick
Disaster Recovery = Backup ( Backup ( Your Backup ) )
July 27, 2019 at 3:01 pm
I approach new releases with seriously mixed emotions.
For example, the move from 2000 to 2005 brought some great and incredibly useful changes to SQL Server. The Windowing Functions are a great example (and your book on them is a must read... thank you for the copy when we first met in person). But, at the same time, they were a bit crippled (could not do a running total, for example) and, frankly, 2005 was pretty much broken until SP1. It also took away a lot like the wonderful search functionality that was built into the {f4} key in the old Enterprise Manager. They took away sp_MakeWebTask (which was an incredible reporting tool if you spent a little time with it) and introduced (IIRC) the PIVOT operator, which everyone raved about but was a mere shell compared to the PIVOT operator of MS ACCESS. And then there are things like the new Cardinality Estimator... that broke a lot of serious stuff for us. Thank goodness they also issued a trace flag that would let us use the old CE.
It also seems that with every release, something works differently and, as we saw with 2012, MS apparently can't even control their source controls not to mention the fact that a new problem of Online Clustered Index Rebuilds would now corrupt your data under certain but common conditions.
And then there's stuff that's documented in such a fashion you can't easily tell what's going to happen and hasn't received all the "new cool feature" attention in blogs so that you're aware of the change. The best example is the bit of mostly unknown horror MS created with the MAX and XML datatypes. Those, of course, are consider to be LOBs and while it was a great change, there's a little dirty secret to it all. The old Text, NText, and Image datatypes defaulted to "out of row". The new MAX (VARCHAR, NVARCHAR, VARBINARY, and XML) default to "in row" and very few people realize the performance and memory/disk space wasted usage horrors that has wrought (all courtesy of "trapped" short rows, which I have been giving a presentation on along with how to fix it).
To summarize...
Or... if you truly want to summarize my feelings about it, "Change is inevitable... change for the better is not" and "Continuous improvement frequently is not". 😉
Either way, I DO strongly agree with the premise of this article and I thank you for taking the time to write it, Kathi... Be aware... be VERY aware of the forthcoming changes.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply