CODEWITHSUNDEEP
sqlsql-serverazureazure-sql-databasebacpac
Jaimin Soni
Jaimin Soni

Reputation: 1071

Count not load schema model from package. (Microsoft.SqlServer.Dac)

enter image description here> ADDITIONAL INFORMATION:

Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service. (Microsoft.Data.Tools.Schema.Sql)

I am getting above error when I am restoring Azure SQL Bacpac file in local environment. I have below environment on Azure and Local.

Azure SQL RTM Version : Microsoft SQL Azure (RTM) - 12.0.2000.8 Aug 29 2017 13:06:11 Copyright (C) 2017 Microsoft Corporation

Local Environment SQL RTM Version : Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49 Copyright (C) 2017 Microsoft Corporation Developer Edition (64-bit) on Windows 10 Pro 10.0 (Build 15063: )

Can anyone please suggest the compatible version of Management studio or SQL RTM for above Azure SQL RTM database restore ?

Upvotes: 8

Views: 14837

Answers (4)

Bamiji O
Bamiji O

Reputation: 1

If anyone has this issue, upgrading to the latest version of Server management studio worked for me (current at the time of writing is 20.1.10.0)

Upvotes: 0

GirishBabuC
GirishBabuC

Reputation: 1379

1st we need to check, In version of .bacpac is creted. the higher version will support lower version of .bacpac, but lower version will not support will higher version of .bacpac.

Upvotes: 0

AlonMichaeli
AlonMichaeli

Reputation: 161

I haven't managed to solve it through SSMS, the only way that worked was through CMD: "C:\Program Files (x86)\Microsoft SQL Server\140\DAC\bin\sqlpackage.exe" /a:Import /sf:PATH-TO-BACPAC-FILE /tsn:SERVER-NAME /tdn:DATABASE-NAME /tu:USER-NAME /tp:PASSWORD

  • Replace the upper-cases with your SERVER/DB info.
  • Use correct folder (110,120,130,140...)

Upvotes: 7

Alberto Morillo
Alberto Morillo

Reputation: 15668

Please download the latest version of SSMS from here, it may solve the issue.

It seems a known issue the error you are receiving. On this Microsoft blog post, they were successful restoring to a SQL Server 2012 instance using SSMS 2014.

You will find more workarounds and solutions on this StackOverflow thread.

Upvotes: 5

Related Questions