When you are developing for the Microsoft Business Intelligence stack, you always needed Visual Studio for your business intelligence (SSIS, SSAS & SSRS) projects. If you have a full blown Visual Studio installation, you needed the BI templates; if you didn’t have Visual Studio (or the right version), you would install a shell that could only be used to develop BI projects.
So far so good, until the notorious marketing department of Microsoft decided to fiddle with the names of said software product. Over 2 years ago, I wrote the blog post SQL 2014 CTP1, where is my BIDS? – one of my most popular posts I might add – where I tried to explain the confusion of yet another name change and also point out how you could get the software. At that point in time – the CTP release of SQL Server 2014 – you had to download the software separately (it was no longer part of the SQL Server set-up) and you had to install it as “a new instance”. Anyway, in this blog post I’ll revisit the subject since there is again (some sort of) a name change.
Let’s give an overview of the SSDT evolution:
To be honest, I think the latest change is great since it has the least amount of confusion. There is now only one installer and you have everything you need. Combine this with the fact that in the future you would only need one version of Visual Studio to manage different versions of SQL Server (which has been announced, but not released yet) and we can admit that Microsoft has finally got it right. At least for the BI development environment that is.
I recently read the book Agile Data Warehouse Design - Collaborative Dimensional Modeling, from Whiteboard…
You can find the slides for the session Building the €100 data warehouse with the…
I was asked to do a review of the book Microsoft Power BI Performance Best…
This is a quick blog post, mainly so I have the code available if I…
Praise whatever deity you believe in, because it's finally here, a tenant switcher for Microsoft…
This book was making its rounds on social media, and the concept seems interesting enough…
View Comments
Great post, Koen. Thanks for sharing!
... but, I won't believe they have it "right" until they bring back colors to the SSIS designer so you can tell disabled boxes from enabled ones! And wow, the limitations here. You have to have Windows 8+ and VS 2015? The SSDT for VS 2013 was not backwards compatible for SSIS in Sql 2008R2 or 2012... is this version?
If that's what the marketing dept looks like, what does the VS architecture team look like? They seem to always forget the BI developers when building the next gen VS
The problem with Visual Studio and SQL Server was that both had different release cycles. Now that SSDT is a separate download this will most likely improve in the future.
They are working on backwards compatibility though, so that's coming in the near future!
Regarding disabled vs enabled: you are absolutely right that it is hard to see. However, I believe you can install custom themes in Visual Studio so that it looks like VS 2010 where this was less an issue.
If you find these magical "themes" ... let me know. I looked for them once, but all I found was a bit about building your own and ... well, I couldn't figure out which color was controlling the disabled/enabled color ... not that I expended much time on it. It is frustrating when things that used to work out-of-the-box, suddenly don't!
Here you go: https://visualstudiogallery.msdn.microsoft.com/366ad100-0003-4c9a-81a8-337d4e7ace05
The editor comes with some pre-built themes. The blue one resembles VS 2010.
It's been a while since I used this, so not 100% sure it will solve the disabled/enabled problem, but it's worth a shot.
Personally I think the notion that they even *have* to come up with a name is dumb. Why do they insist on giving a name something that doesn't need a name? When you install SSDT, SSDT-BI, BIDS etc.. all you're basically installing is an instance of Visual Studio with some project types (SSIS, SSAS, SSRS, SQL Server) in it. That's no different from installing Visual Studio with the C# project type. I never liked the name BIDS either, for exactly the same reason.
Call it what it is. Its Visual Studio. Calling it something else just for people who develop using SQL Server technologies is patronizing. We're all developers, why not treat us all the same?
As ever Microsoft just treat SQL Server developers as second class citizens: http://sqlblog.com/blogs/jamie_thomson/archive/2010/01/12/the-sql-developer-gap-warning-rant-coming-up.aspx
You're right Jamie, but I can imagine that in 2005, putting "Visual Studio" as part of the SQL Server set-up might have been confusing to some people. I've seen clients turn white once I mentioned they need Visual Studio to develop their BI solutions. "Relax, relax, it's a free version of Visual Studio..."