For years, SQL Server included a complete set of add-ons with the main product. We got SSIS, SSRS, and more as part of an integrated installation. This also included things like Books Online and various tools, such as Profiler, bcp, and Management Studio (Enterprise Manager in earlier versions). Over the years, the number of tools has grown, but there has also been work to decouple some of these items from the installation media and allow them to be upgraded more rapidly. Books Online was the first to separate, though not without some pain for users that struggled to install the local help files.
Last year SSMS was decoupled from SQL Server, which I think is a great idea. The tools team at Microsoft moved to their own release schedule, getting SSMS onto the Visual Studio 2015 platform. This wasn't without some pain, and there were definitely some releases with issues, but overall the process has smoothed out and I've appreciated the updates. This separation has allowed new features to be added to the product without waiting for a new release. If you watch the changelog, you will see quite a few improvements and fixes being released, along with enhancements. SSMS is also free to download and install on workstations without SQL Server.
However, if you examine the installation for SQL Server, there are plenty of other products that could benefit from being decoupled. While bcp and sqlcmd don't change much, why are they a part of the server platform? These tools, along with others, are really client side tools, and would benefit from their own release cycles. Whether or not teams do significant work, or even if they only release updates when a new version of SQL Server comes out, having them as a separate set of tools, with a separate installer, means that fixes and enhancements could be sent out if there are issues. This seems especially important for security updates, which might be needed. In addition, maybe this would actually get teams to view any separate tools as worthy of new functionality if they see an opportunity.
I'd actually love to see some integrated installer for the SQL tools that would allow me to download and update them each as needed. Let me know when SSMS is out of date, along with any updates for sqlcmd, sqlmaint, tablediff, and other tools. They might not change often, but I'd rather not have to run the SQL Server installer for a CU on all my client workstations. Let me update those tools as needed, if there are changes or improvements.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
The industry standard for comparing and deploying SQL Server database schemas
Trusted by 71% of Fortune 100 companies, SQL Compare is the fastest way to compare changes, and create and deploy error-free scripts in minutes. Plus you can easily find and fix errors caused by database differences. Download your free trial
If you use an unverified scalar function, then the query will be grindingly slow because you will be executing it on every row whether it has a parameter or not. This post explains the issue in more depth, and shows how SQL Prompt code analysis rules can help you avoid it altogether. More »
While software is among the most widely used products in human history, it also has one of the highest failure rates due to poor quality. In this article, Cynthia Dzikiti explains how quality should be part of all aspects of the software lifecycle. More »
The company's new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced. Get your copy from Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
I have this code, but it's giving me an error after my values clause. What should that line contain?
(SELECT n = ROW_NUMBER() OVER (ORDER BY (SELECT null))
FROM (VALUES (1), (2), (3), (4), (5), (6), (7), (8), (9), (10))
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.