#Microsoft team foundation server 2018 code

Syntactic sugar – There are a bunch of new syntactic constructs, like “drop index if exists” or “create or alter” that we adopted to simplify our code.

#Microsoft team foundation server 2018 code

Page compression – SQL Server 2016 introduced page compression in all editions and we were able to remove our code that conditionalized it.

Changes in date/time computation – We were able to remove/simplify much of our date/time manipulation code due to improvements in SQL Server 2016.CCI existed in SQL Server 2014, however, the implementation was immature enough that we could not use it. The analytics service isn’t enabled in TFS 2018 but the code is in there and our hope is to enable it in a TFS 2018 Update. Clustered ColumnStore Indexes – The plumbing for our new analytics capabilities relies on CCI.I’ll give just a few examples of SQL Server 2016 features that we have taken dependencies on: Unwinding that assumption out of all the code that has been written would be quite a lot of work.

But we made the decision, internally, a year ago to take a dependency on SQL 2016 and all development that happened since then relied on that assumption. Could we have possibly developed TFS 2018 without taking those dependencies? Yes. We decided to leave the requirement because we have taken dependencies on a number of features that are not available in previous versions of SQL Server. We have decided to leave the requirement as it is (SQL Server 2016 or later) but will make some changes in our approach going forward.

I wanted to wrap up that conversation in a very open way with the conclusion we’ve reached. I read it carefully and we discussed it within our team. In the comments, there ensued a sizeable conversation about the requirement for SQL Server 2016 or later (rather than also supporting SQL Server 2014). About 6 weeks ago, I wrote a post announcing the availability of TFS 2018 RC1.