Director of Software Development & Integration for Sta-home Health & Hospice, Inc.Chairman of the Board of Advisors for the Dynamics GP User Group (GPUG)
10+ years with Dynamics-GP (GL, AP, HR, Payroll, Maintenance, Training, Upgrades, Security) 15+ years as a Database Administrator (Maintenance, Performance, Warehousing, Validation, Correctness, Alerts, BI & Reporting)20+ years as a Developer (Written software for IBM, BCBS, Schools, Nursing Homes, & Home Health)
You can follow my blog here or my other networks below:
Any views contained within are my personal views and not necessarily Microsoft policy or the policy of Sta-home Health & Hospice, Inc.All posts are provided "AS IS" with no warranties, and confers no rights.
Blogs Outside of the Dynamics CommunityIn Recovery by Paul RandalSQL Skills by Kimberly Tripp
Post SeriesCreating an EDW for CBI SeriesGetting Data from Point A to Point B
I do not know if everyone has seen this but you really should go take a look!
You can find it here ==> Deprecated Database Engine Features in SQL Server 2012
Now, for me there is not too many things that list that make that much of a difference to me. Things change, that is life. The only constant is change itself.
However, there are some things under the “Features Not Supported in a Future Version of SQL Server” (Deprecated) that I would like to point out so that everyone notices them and gets ready. And you know me, sometime I have got to add my two cents. (Note: In no specific order.)
Feature ID 15 -- The old FILE_ID is changing to FILE_IDEX My 2 Cents, where is the “N” as in FILE_INDEX?
Feature ID 3 -- Three-Part and Four-Part column Reference is going away only Two-Part will be allowed. My 2 Cents, I really hope that this does not mean what I think it does on my first glance. I will have to dig into it some more.
Feature ID <None given> but as I type this it is just under 163 -- End Transact-SQL statements with a semicolon(;) My 2 cents, I really hope that is added to the IntelliSense to automatically do that when I hit the enter key. Otherwise I am in a lot of trouble, and that’s not mentioning all the code I will have to go back and change.
Feature ID 186 -- Use of @, @@ as Transact-SQL identifiers. My 2 Cents, hum, I am going to have to think about that one.
Community Content Section
Now, under the Community Content section, is a comment about Feature ID 112, and while I can see that persons point completely, I have to admit for the most part I actually (and this is IMO (In My Opinion)) choose to disagree.
Please keep in mind that everyone has a right to their opinion and we can all agree to disagree.
But in my humble opinion anything added to NULL should be NULL.
Think about math for a second, and number times zero is zero. Additionally if you try to divide by zero you get an error as you should. So, with that thought in mind, any string plus NULL should be NULL unless you explicitly code something to prevent it like the ISNULL function. If you divide by some variable you should always check that the value of that variable to make sure it is not zero. This at least to me is pretty much the same.
Anyway, these are all just my 2 cents worth at the time of this posting.
I reserve the right to an opinion.
I reserve the right to be wrong. (I am only human after all).
Additionally, I reserve the right to change my opinion as I learn more.
And feel free to comment, send me an email, contact me anyway you wish, and disagree with me. I will be more than willing to listen-n-learn and possibly change my opinion. It has happened lots of times before, and I am sure that it will in the future.
Till later and have a happy holiday,
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics