I only have time for a quick post at the moment, but be aware that if you take advantage of the latest SSMS 2016/Visual Studio 2015 SSDT releases, they do (at last) incorporate the SSDT-BI designer templates. The VS 2015 Report Designer, however, always upgrades the edited RDL file to the 2016 RDL schema. Continue reading →
In the “better late than never” category… (I missed this because I had given up looking for it. Besides, I am presently trapped in RS 2008 RTM hell.) SQL Server Data Tools – Business Intelligence for Visual Studio 2013 SSDT BI – Analysis Services and PowerPivot Team Blog – Site Home …Continue reading →
After installing SQL Server 2012 SP1 on your workstation, an update to SQL Server Data Tools is required before Visual Studio 2010 SP1 can again open BI projects. You can find the SSDT update links for VS2010 and VS2012 here.
Summary: When input to an SSDT DSV involves complex metadata such as nested views and/or MDS subscription views, performance of the DSV ‘refresh’ function may degrade to the point where it is unusable. Simplifying the metadata represented by the input solves the problem.
My migration to SQL Server 2012 has actually been going rather smoothly. The other issues apart from the one I discussed earlier have been relatively minor, although some were time consuming to work out and some were annoying. Here is what I have run into so far:
I originally wrote about this issue in 2010, I continue to see it from time to time, after something “disturbs” Visual Studio. It starts with an alert something like this appearing upon opening Visual Studio or BIDS:
When you begin to use the Visual Studio 2005/8 ReportViewer web control (to view SQL Server Reporting Services reports) you are likely to find that it presents an extra set of scroll bars within the web page, making it hard to use. This is normal and there are several ways to …Continue reading →