March 22, 2018 at 4:37 am
Hello,
After converting my SQL Server Instance from 2012 to SQL Server 2016 (with SP1):
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 Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
We started to have the below error :
The Edition of SQL Server installed on the instance does not support Master Data Services Databases
MDS database can only be installed in SQL Server 2016 Enterprise edition?
Thank you
March 22, 2018 at 4:50 am
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 22, 2018 at 5:12 am
Thank you for the link.
It says only enterprise and dev editions support it.
But I have one dought. Maybe you can help me clarify.
I am not speaking about the application (web application) what I am speaking is about the database it self. So, if we restore the DB into a SQL Server 2016 sp1 it will not work, even knowing that the application MDS it self was not changed, correct?
But with SQL Server 2012 it was not the case, correct? it was supported in SQL Server 2012 standardedition?
March 22, 2018 at 5:21 am
river1 - Thursday, March 22, 2018 5:12 AMThank you for the link.It says only enterprise and dev editions support it.
But I have one dought. Maybe you can help me clarify.
I am not speaking about the application (web application) what I am speaking is about the database it self. So, if we restore the DB into a SQL Server 2016 sp1 it will not work, even knowing that the application MDS it self was not changed, correct?
But with SQL Server 2012 it was not the case, correct? it was supported in SQL Server 2012 standardedition?
Define what you mean by "not work".
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
March 22, 2018 at 5:40 am
We have upgraded all our instances from SQL Server 2012 to SQL Server 2016 SP1.
We have two different situations here:
1) In DEV environment I am getting this error after restoring the DB:
The client version is incompatible with the database version. Ask your administrator to upgrade the client components, the database components, or both. Run the Master Data Services Configuration Manager on the server for more information. Client Version - 11.0.5058.0 ; Database Version - 11.2.0.0
2) In test environment we have this error after the restore:
The edition of SQL Server installed on the instance does not support Master Data Services Database
March 22, 2018 at 5:44 am
It seems to me, from reply gaven by Gila that if we restore a Master DB database into a SQL Server 2016 sp1, even not having touched in the application (Master Data Services Web), still we will not be able to connect as it seems probably the application before connecting to the DB will check if this is enterprise edition or not and that was not happeing in SQL Server 2012.
Very strange is also the error in DEV environment after the restore of DB into the new SQL Server 2016 SP1 instance, this one seems not related with the SQL Server version.
Can you please help?
Thnak you.
March 22, 2018 at 5:54 am
river1 - Thursday, March 22, 2018 5:12 AMThank you for the link.It says only enterprise and dev editions support it.
Correct. It does.
The very first entry in the table explicitly says that the database is only Enterrprise/dev editions.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 22, 2018 at 5:59 am
Have a look in the MDS configuration tool and you might have an upgrade button for the error:
The client version is incompatible with the database version. Ask your administrator to upgrade the client components, the database components, or both
I’ve had something like that before when applying a sp or cpu patch
MDS needs EE or use the development version.
March 22, 2018 at 6:00 am
river1 - Thursday, March 22, 2018 5:44 AMIt seems to me, from reply given by Gila that if we restore a Master DB database into a SQL Server 2016 sp1, even not having touched in the application (Master Data Services Web), still we will not be able to connect as it seems probably the application before connecting to the DB will check if this is enterprise edition or not and that was not happening in SQL Server 2012.
It sounds likely that this is the correct explanation. You may have to consider maintaining your 2012 instance for MDS only.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
March 22, 2018 at 6:06 am
I checked and MDS need EE on 2012
MDS on 2016 is heaps better, faster and the business rules are easier to use plus you can have tsql based rules.
Still need silver light and slowly changing dimensions are not supported which are the only gripes I have ATM
March 22, 2018 at 7:51 am
Yes. That explains the test error. but not the dev error 🙁
I don't understand this one: The client version is incompatible with the database version. Ask your administrator to upgrade the client components, the database components, or both. Run the Master Data Services Configuration Manager on the server for more information. Client Version - 11.0.5058.0 ; Database Version - 11.2.0.0
Can we have a client version different from DB version and still, be able to connect? probably yes and then we just need to do a repair DB but I am not sure...
Can you help me understand that?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply