Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2012 Forums
 Other SQL Server 2012 Topics
 SQL Server 2012 SP1 CTP4

Author  Topic 

mauisys
Starting Member

7 Posts

Posted - 2012-11-19 : 18:14:35
Hi,

I installed SP1 CTP4 to SQL 2012 but I do not see compatibility level of 1100 or 1103 as expected. I still see compatibility levels of 100 and 110.

When I run select @@version I get:
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2)

Anyone else run into this?

Any idea what I'm doing wrong??

Thanks.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-11-19 : 18:54:04
I don't think those compatibility levels are available in the database engine. Maybe you are referring to SSAS?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

mauisys
Starting Member

7 Posts

Posted - 2012-11-19 : 19:09:23
Tara,

Yes, SSAS - sorry...

Using Server Management Studio I connect to my SSAS instance and I can see Supported Compatibility Level is 1103 (Right click on the Server\Instance and click properties). But when I right-click on the actual database and look at properties and Compatibility Level is 1100. I'm not sure how to change it to 1103.

I'm trying to test the Excel 2013 PowerView features. One thing in particular is that Hierarchies and KPIs that are built in the model are not recognized by Excel 2013 unless the compatibility level is set to 1103 (SP1).

Thanks,
Dave M
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-11-19 : 19:13:50
Does this work? http://msdn.microsoft.com/en-us/library/bb510680.aspx

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

mauisys
Starting Member

7 Posts

Posted - 2012-11-19 : 19:29:19
Negative.

Here is my query:
ALTER DATABASE [AW Internet Sales Tabular Model]
SET COMPATIBILITY_LEVEL = 1103

This is the error that is returned:
Msg 15048, Level 16, State 1, Line 1
Valid values of the database compatibility level are 90, 100, or 110.
Go to Top of Page

mauisys
Starting Member

7 Posts

Posted - 2012-11-19 : 19:32:15
Here is a link to the blog post that I was trying to follow to resolve the issue:

http://denglishbi.wordpress.com/2012/10/04/tabular-models-compatibility-level-and-power-view/
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2012-11-19 : 19:39:58
Sorry I'm unable to help. I don't have any experience with SSAS.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2012-11-20 : 03:32:12
quote:
Originally posted by mauisys

Tara,

Yes, SSAS - sorry...

Using Server Management Studio I connect to my SSAS instance and I can see Supported Compatibility Level is 1103 (Right click on the Server\Instance and click properties). But when I right-click on the actual database and look at properties and Compatibility Level is 1100. I'm not sure how to change it to 1103.

I'm trying to test the Excel 2013 PowerView features. One thing in particular is that Hierarchies and KPIs that are built in the model are not recognized by Excel 2013 unless the compatibility level is set to 1103 (SP1).

Thanks,
Dave M


DId you change compatibility level as article suggested in tabular model project before deploying to server?

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2012-11-20 : 03:33:21
The change has to be done in model property settings and not at database instance level which was what you were trying to do with ALTER DATABASE statement earlier

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page
   

- Advertisement -