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.
Related
I am trying to connect to a Microsoft SQL Server database through Oracle SQL Developer (version 4.2), after adding 3rd part JTDS jar 1.3 version.
After adding the connection details under the SQL Server tab, I am getting this error while retrieving database:
Error: the target database is in an availability group and is currently accessible for connections when application intent is set to read only.
Where and how to add application intent?
I am unable to see any advanced connection properties button which are there in Microsoft SQL Server Management Studio in which I am able to connect via setting applicationintent=readonly.
Thanks.
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'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.
Environment: Windows 7 Professional 64bit, SQL Server Express 2014 64bit with Advanced Services, Visual Studio 2013 Professional.
I imported some MS Access reports to SQL Server Express 2014 Reporting Services. The report runs fine in VS2013 but when I run the report in the Report Manager by just clicking the report in the Reports folder, I get the following error:
An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'OLEDB' that is either not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound)
I can see the entry for 'OLEDB' in the Extensions node of the the reportserver.config file.
What could be causing the error and how can we remedy it.
EDIT 1:
After migrating the reports from Access Db I changed the Db connections to local SQLEXPRESS Db. The reports are connecting to the local SQLEXPRESS db and are displaying the data fine inside Visual Studio 2013.
EDIT 2:
I downloaded the report from the Report Manager and opened it XML mode and noticed that the Data Source of the report is actually is the Access Db that I imported the report from. According to a comment from Sébastien Sevrin SSRS in SQL EXPRESS does not support Access Db as a Data Source, hence the issue.
What could be causing the error?
The cause of this error is that SQL Server Express only supports Datasources located in the Local SQL Server instance.
How can we remedy it?
You have 2 options:
Upgrade to a Standard version of SQL Server at least
Target a supported data-source (SQL Express)
More info: Features Supported by the Editions of SQL Server 2012
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.