For nearly half of my life, I've looked forward to new versions of SQL Server. At first I was just hoping to see SQL Server run on a stable OS, as the OS/2 1v.3 was my original installation. That system couldn't run 12 hours without someone restarting it, and the upgrade to SQL 4.2b and OS/2 2.1 was welcome. That change reduced my schedule below the 100hr/week level. It wasn't long after that we upgraded to Windows 3.1 Advanced Server, and never looked back. Since then, I've upgraded through all the versions since. From 6.0 to 6.5 to 7.0, and then all the 200x versions.
This week, Microsoft announced the general availability of SQL Server 2017 will come on Oct 2, 2017. This will also be the version that debuts on Linux and in Docker. I've been running SQL Server on Linux, and overall, I enjoy it. I've experimented with Docker, and since I often have multiple versions running, I think containerized SQL Server is likely the way to go for development systems. Perhaps even further downstream at some point. We'll see, as I'm not completely sure that containers are the best choice for database systems, but I am considering them as a possible replacement for VMs.
I haven't always thought every upgrade of SQL Server was worth installing for many data professionals. I think a few versions were really point releases, incorporating limited changes that affected few people. For my own systems, I've often looked to skip a version, though that depends on my needs. I think SQL Server 2005, 2008, 2012, and 2016 were worthwhile upgrades with lots of new features. However, some of those features are immature, so perhaps 2008 R2, 2014, and 2017 were better choices for moving your production systems.
There aren't a lot of changes in SQL Server 2017, but the addition of Linux and the query plan improvements will be helpful to many of us. If you are looking to install a new system, take a look at this version. It's a more solid SQL Server 2016, even if you don't need the new features. I am happy that Microsoft is releasing more often, giving me the option of adopting new features quicker. I don't know if I'd want something like graph database capabilities, but I'm glad I get the choice in 2017 rather than having to wait until 2019 or 2020.
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
How difficult can it be to produce a simple hierarchical list in JSON, YAML, XML and HTML from a SQL Server table that represents a simple hierarchy within an organisation. Well once you know, it is easy and William Brewer is on a mission to tell you how. More »
Whether you’re only just starting to explore the advantages of DevOps or you’re already fully immersed in the journey, including the database brings additional advantages. Take a few minutes to complete our Database DevOps Maturity Assessment and you’ll better understand how advanced your current processes are, receive recommendations for improvements, and see how your maturity level compares with that of your peers. More »
Automate your workload and manage more databases and instances with greater ease and efficiency by combining metadata-driven automation with powerful tools like PowerShell and SQL Server Agent. Automate your new instance-builds and use monitoring to drive ongoing automation, with the help of an inventory database and a management data warehouse. Get your copy from Amazon today.
Yesterday's Question of the Day
(by Steve Jones):
I have a CSV with a number of rows and columns that looks like this:
I want to read this into a dataframe in R. What command should I use? Assume the filename is c:\nfl\2016qbstats.csv.
Powershell to get Results and Messages in SSMS inquiry
- I have a powershell script that will execute a query on a database that has Replication.
$QueryPath = "C:\Replication\RepAsPub.sql"
$OutputFile = "C:\Replication\RepAsPub_Result.csv"
$ExecuteQuery = Get-Content...
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.