What's new in SQL Server 2016

James Serra posted a SlideShare covering what's new in SQL Server 2016, including the recently released SP1.  SP1, BTW, opened up just about all the features to all versions of SQL Server.

If you like slide shows that outline the latest with SQL Server, take a look at the SlideShare on LinkedIn.  You can find it here:

What's new in SQL Server 2016 - James Serra

Index usage stats for SQL Server

Need information on if your indexes are being used?  Greg Larsen has posted a query utilizing the DMV sys.dm_db_index_usage_stats.  You can find it here:  Which Indexes are not Used? - Greg Larsen

SQL Server v.Next CTP 1.1 released

Microsoft released the first update to the Linux v.Next version of SQL Server, officially lised as SQL Server v.Next Community Technology Preview (CTP) 1.1. From the announcement, the key database engine enhancements include:

Key SQL Server v.Next CTP 1.1 database engine enhancements include:

• Language and performance enhancements to natively compiled T-SQL modules, including support for OPENJSON, FOR JSON, JSON built ins as well as memory-optimized tables support for computed columns.
• Improved the performance of updates to non-clustered columnstore indexes in the case when the row is in the delta store. 
• Batch mode queries now support "memory grant feedback loops,” which learn from memory used during query execution and adjusts on subsequent query executions; this can allow more queries to run on systems that are otherwise blocking on memory.
• New T-SQL language features:
• Introducing three new string functions: TRIM, CONCAT_WS, and TRANSLATE
• BULK IMPORT supports CSV format and Azure Blob Storage as file source
• STRING_AGG supports WITHIN GROUP (ORDER BY)s
• Most of the improvements in SQL Server 2016 Service Pack 1 are now available in SQL Server on Linux, with the exception of a few features such as Polybase 

Source:  Microsoft community update email: Dec 19, 2016

How to Update -  See:    Update SQL Server on RHEL - CentOS

Update SQL Server on RHEL - CentOS

Sourced from the Microsoft support documents:

Notes:  

1) No restart/reboot after running the update command
2) Microsoft's posted command uses yum update, not yum upgrade.

    "In order to upgrade the mssql-server package, execute the following command:

   sudo yum update mssql-server

These commands will download the newest package and replace the binaries located under /opt/mssql/. The user generated databases and system databases will not be affected by this operation."

Source:

https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-red-hat#upgrade-sql-server-on-red-hat-enterprise-linux

SSMS vNext and "Cannot connect to WMI provider"

Problem:  

After installing SQL Server Management Studio for vNext, the Configuration Manager no longer opens, with a message similar to the following:

             Cannot connect to WMI provider. You do not have permission or the server is                        unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.

Invalid namespace [0x8004100e]

Steps to correct:

1. Search for the file:  sqlmgmproviderxpsp2up.mof
   You will probably find it in the folder:
   
      C:\Program Files (x86)\Microsoft SQL Server\140\Shared

1. Run the following command, adjusted using the file location from the search above.
   
   C:\WINDOWS\system32>mofcomp "%programfiles(x86)%\Microsoft SQL Server\140\Shared\sqlmgmproviderxpsp2up.mof"

Based on Microsoft support - kb966013:

Error message when you open SQL Server Configuration Manager in SQL Server: "Cannot connect to WMI provider. You do not have permission or the server is unreachable"

Linux - SQL Server Service: Status - Stop - Start - Restart Commands

A listing of commands to check the status of the SQL Server service, along with stopping, starting and restarting the service (RHEL):

Status Check

                 systemctl status mssql-server -l

Start Service

                 sudo systemctl start mssql-server

Re-start Service

                 sudo systemctl restart mssql-server

Stop Service

                 sudo systemctl stop mssql-server

Database Uptime vs. Aircraft Engine Maintenance

Brent Ozar has a great way to compare maintaining databases to maintaining aircraft engines. It goes like this:

"...if you have an airplane, it’s absolutely imperative that its engines not fail mid-flight. In order to accomplish that, you have to have regular downtime for mechanics to examine and replace parts – and that doesn’t happen up in the air. 

With Availability Groups, we’re lucky enough to be able to transfer our passengers databases from one airplane to another quickly – but we still have to have those other airplanes getting constant examinations and patches from mechanics." (Brent Ozar, December 7, 2016)

You can read the full posting at:  Availability Groups: More Planned Downtime for Less Unplanned Downtime