Over the years, Unified Logic has followed the evolution of SQL Server from a row-store RDBMS to the database of choice for on-prem and cloud deployments. At the same time, we have witnessed the rise of third parties and ISV’s that use SQL to support their applications, and as a result we have developed intelligent queries to extract data from systems such as vCenter, Altiris, BigFix, and many more in order to provide customers with visibility that was previously not possible.
Through the data collected by Movere, we have been monitoring the adoption of SQL Server by version and for the first time we have seen SQL 2012 and above reach 35% adoption which is a great milestone for many reasons.
SQL 2012 brought huge enhancements to make SQL Server a real contender in the database space. It introduced features such as Column Store Indexes (for more on that read https://en.wikipedia.org/wiki/Column-oriented_DBMS) and Pagination (http://www.sqlshack.com/sql-server-2012-introduction-pagination/) that enabled its fast adoption. SQL Server 2014 brought an amazing new feature as well: In-Memory OLTP (https://msdn.microsoft.com/en-us/library/dn133186.aspx), but at the same time had some limitations (256 GB for in-memory tables, lifted to 2 TB in 2016).
Another (lesser known) fact is that SQL Server 2012 brought in several security enhancements, one of them being the removal of Windows accounts from having access to SQL by default. One of these accounts is the Windows System account (NT Authority) which as you know is what Movere uses as the default account to perform inventory. Movere already supports additional user accounts through the Console, however the default scanning method leverages the Windows System account for all data points gathered (SQL included). This had its benefits up until recently when we noticed that the proportion of new SQL installs (2012 and above) to old (2008 R2 and below) has changed drastically in favor of 2012 and 2014. At this pace, we predict that the ratio will be 50:50 by mid-2017 and from that point on the decline of older versions of SQL will be accelerating at exponential rates.
What does this mean for Movere?
For SQL 2012 and above…
- Movere will leverage the first Windows Domain credentials provided and then loop through any additional Windows Domain credentials provided for domain-joined devices.
- Movere will use any SQL (i.e. “sa”) credentials provided. This can be useful for customers that do not have Windows Administrator access (user or group level) to SQL Server or customers with non-AD joined devices.
- Movere will lastly use the Windows System account.
For SQL 2008 R2 and earlier…
- Movere will continue to leverage the Windows System account first and then loop through any other credentials provided (Windows Domain or SQL).
This should ensure a much higher success rate on the first try for gathering SQL data, and we urge you to educate users on the above connection options. Also, please note that Movere will continue to require minimal access (read-only = dbdatareader) when accessing data from customer databases, as well as from SQL built-in databases such as “master” and “msdb”.