I've created an new SQL V12 database on azure. I've been enabled to update that database once to the model we have in our database project. We did this by using the 'Register as Data-tier Application' in SQL Management Studio.
Now we have an update on our model and we want to update our database again with a new DACPAC. When we use the function 'Upgrade Data-tier Application' (again trough SQL Management Studio) we get the error message:
TITLE: Microsoft SQL Server Management Studio
Databases registered as a DAC database must be hosted by an instance
of SQL 2005 SP4, SQL 2008 SP2, SQL 2008 R2, SQL 2012, SQL 2014 or
Microsoft Azure SQL Database. (Microsoft.SqlServer.Dac)
------------------------------ ADDITIONAL INFORMATION:
Unable to proceed with DAC operations on the target instance because
it does not support DACs. Specify another instance, or upgrade to a
version that supports DACs. (Microsoft.Data.Tools.Schema.Sql)
Very strange notification cause the database is already registered as Data-tier application and has been deployed once. I can't find any logs giving more details.
Our Database project has the target platform: "Microsoft Azure SQL Database V12" so that is the correct one.
Did you get anywhere with this? I'm encountering the same error. Need Azure SQL V12 so I can include Always Encrypted CMK/CEK and column encryption settings with the dacpac. Also, I'm deploying to a
I tried deploying from SSMS 17.2 and VS2015 w/ SSDT 14.0.61021.0 with no success.
I had originally published to the same DB with the DACPAC target as "Azure SQL Database" (not V12). Then later needed to change to V12 so I could build the dacpac with CEKs, CMKs and column encryption settings. After changing to V12 I started getting the same failure message.
I was able to publish for V12 target from VS2015 SSDT to the existing DB if I unchecked the "Register as Data-tier application" checkbox.
Also, I created a new DB and made my first dacpac deployment the one targeting V12 and it succeeded as well. I would think the dac framework would be able to handle the target Azure SQL DB to Azure SQL DB V12, but it seems not.
Hope this helps you or someone else that runs into this.
Related
I am trying to create new SQL Azure database using dacpac file created from local SQL server database using SSDT .
I am getting error as
Publish failed.An error occured during deployment plan generation. Deployment cannot continue. A project which specifies SQL Server 2017 as the target platform cannot be published to Microsoft Azure SQL Database v12.
But did not get any option to choose while doing Extract Data-tier Application to generate dacpac.
Below is error while creating Azure SQL database :
You can do this workaround, you can go into the json file for the project and manually target V12. Edit the sqlproj file.
<DSP>Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider</DSP>
I'm trying to migrate our Access Database to a database on SQL Server 2008 R2.
When I try to migrate it, I get an error message:
You cannot connect to an older version (SQL Server 2008) of target SQL Server from a higher version SSMA project (Project type = SQL Server 2014)
I downloaded and did a 'Typical' installation of 'Microsoft SQL Server Migration Assistant v5.3 for Access' but when it loads, I get the loading screen for a brief second that says 'Microsoft SQL Server 2014' and then the Migration Assistant loads.
I try and migrate my databases but at the end, I get the above error message.
I have MS Sql Server 2014 Management Studio installed on my computer. Perhaps, the migration assistant is using the native engine to load the Migration Assistant? Anyone have any ideas how to fix this?
During the migration, you get a screen where you can specify the Migration name and the path for the Migration Project. In that same window, there is another drop-down where you can specify what you would like to migrate to. The choices are SQL Server 2014, 2012, 2008 and 2005.
I selected 2008 from the drop-down in the 'Migrate To:' field and clicked on Next.
Migration was eventually successfully completed.
I have downloaded ".bacpac" from the resource and i have successfully imported it in "Microsoft SQL Server Studio 2014" using data-tier application. But when i am trying to upload the same file from the "Microsoft SQL Server Studio" to Azure, it's throwing the following error.
It's showing operation failed at "creating database on target". When i am clicking the error link it's showing:
An exception occured while executing a Transact -SQL statement or batch.
(Microsoft.SqlServer.Connectioninfo)
Additional Information
'Web' is not a valid database edition in this version of sql server.(Microsoft SQL Server, Error: 40633)
The Web and Business Azure SQL Database tiers have been retired by Microsoft.
Currently, SQL Server Management Studio 2014 only presents the Web and Business tiers as options when deploying a database to Azure, both of which will be rejected with the "not a valid database edition" message.
The current CTP of SQL Server Management Studio, which can be downloaded from here, does allow you to select the newer Basic/Standard/Premium tiers when deploying a database to Azure, which should work and not produce the error described above.
When you choose the option to deploy the database to Azure in SQL Server Management Studio it will prompt you for deployment settings. e.g. where you would have provided you database credentials. One of the values specified in that window is "Edition of Windows Azure SQL Database" and this may have defaulted to "Web". This could be the reason you are getting the error. Try changing this setting to a more suitable value, e.g. "Standard", and re-deploying the database to Azure.
I was developing an MVC application with SQL 2014. I have used database first approach and generated edmx from my locally hosted SQL 2014 database. So the application was running fine with this local database and default instance.
But yesterday I added my project from my Visual Studio 2013 to TFS 2013(installed on our company server). The addition was successful but when I tried to run my solution it gave the instance error. The SQL instance used by server is:
PEARLSERVER\SQLEXPRESS
Moreover when I tried to install SQL 2014 on our server, it neither asked for authentication type nor any instance. And the version mentioned after installation was of SQL 2012(Our server has already installed SQL2008, SQL2012). What could be the problem? What should I do? Should I add files to TFS from server or generate edmx again from server?
I'm trying to export a DB from my local SQL Server to Azure SQL.
So far I've tried
Tasks > Deploy Database to Windows Azure SQL Database
I then connect to the Azure DB, give the new DB a name and then let it run.
However, it fails with the message
A project which specifies Microsoft Azure SQL Database v12 (Preview) as the target platform cannot be published to Microsoft Azure SQL Database.
Having followed this page, I'm pretty sure that I have the latest of whatever I need on my local.
So what am I missing? How do I get a DB from a local instance of SQL Server to Azure SQL?
Although there are several means to upload a local DB to Azure, I found that all but one of these fails with the same error message.
The one which worked is the SQL Database Migration Wizard.