With the release of SQL Server 2017, Reporting Services is now a separate installation. The installer can be downloaded from the Microsoft Download Center and installed in either a free edition (Evaluation, Express, or Developer) or a paid edition with a product key. It can also be installed silently, and in this blog post, I … Continue reading Silent Installation and Configuration for SQL Server 2017 Reporting Services
The 15.5 release of SQL Server Data Tools for Visual Studio 2017 is the first release to support SSRS, SSAS, and SSIS in VS 2017. The command line below shows how to install all SSDT components in the only installation of VS 2017 on a machine: To work offline, you'll need to create a layout … Continue reading Silent, Offline Installation for SSDT 15.5 for Visual Studio 2017
Day 1 of Microsoft Connect 2017 was today. What a slew of announcements and new products/services! Here is my top 3: Visual Studio Live Share Don't tell me, show me! Share the current state of your code and debugger with someone else, next to you or across the world. It's for both Visual Studio 2017 … Continue reading Microsoft Connect(); 2017 Day 1 Announcements
Based on this question in the Microsoft Forums and the answer from Microsoft in a related Connect feedback item, you can install the Developer edition of SQL Server 2016 or 2017 silently using the Evaluation edition media if you specify the product ID (PID) of 22222-00000-00000-00000-00000. You will either specify this on the command line … Continue reading Silent Installation of SQL Server 2016 or 2017 Developer Edition from Evaluation installation media
File this in the category of error messages that don't really mean what you think. When configuring a failover group using Azure SQL DB, you need to provide a "name" for the failover group. However, the name really becomes the FQDN of the failover group, but that's not directly obvious. The implication of that is … Continue reading Azure SQL DB: The specified failover group name is already in use
I was having trouble connecting with the Remote Desktop protocol to a server. The error returned by the Remote Desktop Connection Manager was 7431. Using mstsc.exe the error was more descriptive and indicated a time difference between the client and the server. I verified that the time difference was not the case. Coincidentally, a support … Continue reading Remote Desktop Error 7431 may indicate a DNS problem
As announced before, I will be speaking once again at the annual Atlanta SQL Saturday. The Atlanta MDF is a great group and they put on an excellent event each year. Note: this year, the venue has changed for the first time in as long as I can recall. Be sure to check the location: … Continue reading Speaking at SQL Saturday #652 Atlanta 2017
