In my post two days ago on silently installing SQL Server 2017 Reporting Services (SSRS 2017), I just provided the most basic information on configuration. In fact, after installing SSRS 2017, it will be completely unconfigured. Configuration can be done using the Reporting Service Configuration Manager GUI. In my case, the configuration needs to be … Continue reading Complete automated configuration of SQL Server 2017 Reporting Services
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
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
SSMS 17 was released today. This is a quick first look at some of the additions and changes that immediately stand out to me.
I don't post about my speaking engagements frequently enough. I realize I should do better and why not start today? I will be speaking at SQL Saturday Birmingham 2017 tomorrow, March 18. I have a single session titled "12 things to know about Azure SQL DB." I got started with Azure SQL DB about two … Continue reading Speaking at SQL Saturday Birmingham 2017
I ran into this problem today that didn't take a long time to resolve, but took me a little by surprise. Most of my SSIS packages use the Lookup transformation component to look up keys used in source systems and match them to the data warehouse. When SSIS packages fail at the Lookup component, the most common cause is that the source system's key does not exist in the data warehouse and must be added first. This time was different, however.