Each new release of Windows is almost as bad as a new product instead of an upgrade. While I appreciate new functionality, upgrades are frequently expensive because of the removal of deprecated functionality. Because, for Windows users, Microsoft has a bit of a corner on the market, they seem to do whatever the hell they want without any concern for the customers that have been so very loyal (willingly or not) over the years.
I also cannot understand the lunacy that appears to be driving supposed improvements. For example the DATETIME datatype very nicely follows simple spreadsheet capabilities, which also mean ISO standards, for STARTDATETIME+PERIOD = ENDDATETIMEand ENDDATETIME-STARTDATETIME = PERIOD. Such simple temporal math is no longer possible with the DATE or the DATETIME2 datatypes.
Another great example of design lunacy came with the release of PIVOT. Microsoft owns MS ACCESS and yet they seemed to ignore the extreme and very simple to use functionality of PIVOT there when the designed the computational travesty of PIVOT in T-SQL.
The thoughtless, apparently market driven, design lunacy continues with such things as not returning an ordinal position for their SPLIT_STRING() function and the fact that the "new' FORMAT function takes 44 times longer to format than the ol' CONVERT() function does just to name a few of many examples of "what the hell were they thinking" designs.
The really bad part of all of this is that most people are deeply invested in the Microsoft stack and, since most of their associates are also invested in the same stack, they need to continue to drink the Kool-Aid that MS has served up, no matter how ridiculous it may be, to be able to communicate and stay in business with dependencies on that stack.
Now they're even making it so that you MUST upgrade to the damned awful Window 10 if you want or need to upgrade to the latest version of Office or expose all your goodies to the security horror known as Office 365.
Microsoft has always been a bit pushy but, especially lately, they've become a damned bully to drive sales through a captive audience.
Oddly enough, MS can't even follow their own deprecation suggestions. Take a look at the stored procedures MS still uses in SQL Server and look for semi-colons.
Between the half-assed, half-fast, and half-done code that MS has been pushing lately, I'll be surprised if anyone can write code that works the first time in the future. Let's hope that none of that is military or critical civilian code, although I think it may be too late even for those.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair
When you put the right degree of spin on it, the number 318
is also a glyph that describes the nature of a DBAs job. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs