Got this error when trying to create a column store index on a fact table:
Msg 35315, Level 16, State 1, Line 1
CREATE INDEX statement failed because a columnstore index cannot be created in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions.
This is from select ##VERSION
Microsoft SQL Server 2012 (SP1) - 11.0.3381.0 (X64)
Aug 23 2013 20:08:13
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
SQL Server Standard edition doesn't support columnstore indexes. From the version comparison for SQL Server 2012, you need Enterprise edition.
Although SQL Server 2012 is specified here, it's worth noting that SQL Server 2016 with Service Pack 1 now allows columnstore indexes to be created across all editions. See here for further details.
Related
Is SQL Server Express edition (2014) not supporting compression at all ?
(Is it necessary to upgrade to enterprise edition)
With Express Edition, you need SQL Server 2016 SP1 or later to support data compression. In earlier versions, you need Enterprise (or Developer for testing). The documentation below detail the features that may vary by SQL Server version and edition:
SQL Server 2014 Features by Edition
SQL Server 2016 Features by Edition
SQL Server 2017 Features by Edition
For our production DB, we are on the following SQL version,
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64) Sep 21 2011 22:45:45
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
From Microsoft KB:
https://support.microsoft.com/en-sg/help/3135244/tls-1-2-support-for-microsoft-sql-server
This SQL Server version is lower than the first build that supports TLS 1.2,
I don't think it supports TLS 1.2.
Can anyone confirm this?
I'm comparing the version numbers 10.0.5500.0 vs 10.50.6542.0 (minimum build that supports TLS 1.2)
SQL Server 2008 v10.0.5500.0 is SQL Server 2008 with Service Pack 3 (SP3) applied. SQL Server with a version number 10.50.xxx.xxx would be SQL Server 2008 R2 - and yes, that's a different version (not just a service pack) of SQL Server.
If you look further down in that document you linked, there's also a line for SQL Server 2008:
SQL Server 2008 SP4 10.0.6547.0
So you would need to apply SP4 to your SQL Server 2008 instance (and possibly also that update that is linked in your document) in order for it to support TLS 1.2
I am trying to create a simple node table, using:
CREATE TABLE Person (ID INTEGER PRIMARY KEY, name VARCHAR(100)) AS NODE
But whatever I try I get an error:
Incorrect syntax near the keyword 'as'.
as if it doesn't understand the 'As Node' part.
I am using SQL Server 13.0.1601.
Database compatibility: SQL Server level 2016(130)
SSMS: v17.2
##version: "Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64) Apr 29 2016 23:23:58 Copyright (c) Microsoft Corporation Express Edition (64-bit) on Windows 10 Pro 6.3 (Build 14393: ) (Hypervisor)"
You can't do CREATE TABLE (SQL Graph) in earlier versions of SQL Server, because it applies to SQL Server 2017.
See the documentation.
I just installed SQL 2016 Standard Edition because I wanted to use the 'Always Encrypted' feature.
However, when I tried to created a Column Master Key under Security->Always Encrypted Keys->Column Master Key, I got the following error:
productversion: 13.0.160.5, productlevel:RTM, edition:Standard Edition 64bit
Any ideas? Thanks!
I was having the same issue. I fixed it by updating to Sql Server 2016 SP1 from Sql Server 2016.
Previously ##version was:
Microsoft SQL Server 2016 (RTM-GDR) (KB3194716) - 13.0.1722.0 (X64) Sep 26 2016 13:17:23 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows 10 Pro 6.3 (Build 14393: )
Now ##version is:
Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) Oct 28 2016 18:17:30 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows 10 Pro 6.3 (Build 14393: )
Note also that my SSMS is totally up to date.
Tools > Check for Updates > Details - 13.0.16100.1
A coworker has a slightly older build of SSMS and does not even see the option to encrypt columns.
The issue was probably caused by restoring a SQL2014 database. I backed up a 2014 database and then restored it in 2016. SQL may have seen it as a 2014 schema and therefore complained Column Master Key not supported.
How I resolved it: In SSMS 2016, generate .sql script for the imported database (in Advanced settings, choose SQL 2016 script)
Install a new SQL 2016 instance (which may not be necessary will test) and run the .sql generated, rather than the restore option
"Always Encrypted is available in SQL Server 2016 (13.x) and SQL Database. (Prior to SQL Server 2016 (13.x) SP1, Always Encrypted was limited to the Enterprise Edition.)"
Source: https://learn.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-2017
In SQL Server 2008 R2 Standard Edition:
SELECT ##version
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)
with non-express edition tools:
Microsoft SQL Server Management Studio 10.50.2500.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .NET Framework 2.0.50727.5448
Operating System 6.1.7601
running on Windows Small Business Server 2011 Standard 64-bit:
Against a database in SQL Server 2000 compatibility mode:
If I try to run the Index Usage Statistics report I get the error:
How to make it go away?
I threw in every red herring I could think of. There should be enough extraneous information that everyone can throw out a theory.
The various reports in SQL Server Mgmt Studio make use of DMV (dynamic management views) like the sys.dm_db_index_usage_stats to fetch their data.
Those DMV are only available if you're running on compatibility level 90 (SQL Server 2005) and up. You won't be able to get this to work if you're stuck in SQL Server 2000 compatibility level (80), unfortunately.