I'm trying to move my databases to a newer Azure subscription. I used to simply click "Deploy to Azure" on a local database from SSMS and have it deployed to a specified Azure server. Importing/Exporting a BACPAC file also works. However, I can't seem to do any of this on the new server. I keep getting the error:
"The service objective 'Web' specified is invalid."
Googling around, I found this thread explaining the need to update the CREATE DATABASE template to accommodate Azure Databases (Azure upgrade, I'm guessing). However, the hotfix provided is specifically for SQL Server 2014 and I'm using SQL Server 2012. I checked other cumulative updates for 2012 here but found no fix for the issue.
Is there any other way I can fix this without having to upgrade to 2014?
Just to summarize my software versions:
SQL Server 2012
SQL Management Studio 11.0.2100.60
Local database: SQL Server 10.50.16000
Old Azure server: SQL Server 11.0.9230
New Azure server: SQL Server 13.0.15
You are getting this error because the latest V12 servers are not supporting the Web and Business Editions anymore. If you don't want to upgrade to SSMS 2014, you can create a V11 server and import your DB on this server. However this is only a temporary solution as Web and Business edition databases will be retired in September. At this point you will have to work with the latest tools to avoid this problem.
There is a Hotfix for it you can download and install on your machine. Please navigate to:
https://support.microsoft.com/en-gb/kb/2936603
You need to enter your email then download link will be sent to your email address. Then install it on your machine and you can see the following options:
Install the database as a Data Project into Visual Studio,
Set the target framework in the properties window to SQL Azure,
Build the project and resolve any unsupported issues.
Publish to your azure site.
I have tried the above and did not work for me - this solution worked!
Related
After installing SQL Server 2019 & SSRS 2019 developer editions, I am not able to use the object explorer in SSMS to connect to SSRS. (I am also unable to use a web address to open SSRS currently due to my security software.) I think the reason I can't use SSMS is due to one or more of the following:
an error in installation
problems with older version files still left on the computer
an error in using the report server configuration manager
the rsreportserver.config file not getting properly updated.
Before installing 2019 developer editions, I have installed and tried to uninstall most versions since 2012, including 2019 express & evaluation. When I tried to install 2019 evaluation software, I created a new db engine (MSSQLSERVER02) while installing SQL Server. After I installed SSRS, I used the report server configuration manager to use this new engine as the database). This tested correctly. I opened up SSMS & connected to this db engine. When I tried to go to SSRS, the only option was a previous db engine (MSSQLSERVER01). Though I put the new name in the config mgr, there still existed an rsreportserver.config file which had the old db engine (MSSQLSERVER01) and a coded database name.
When I uninstalled the eval ed., then installed the dev versions, I still had the same problem with the old db engine (MSSQLSERVER01) name appearing. When I chose the older db option, I get a lengthy error:
Cannot connect to LAPTOP-999999\MSSQLSERVER01. Unable to connect to the server at LAPTOP-999999\MSSQLSERVER01. The specified URL might not be valid or there might be a problem with the report server version or configuration. Specify a different URL, or contact your server administrator to verify that the report server runs SQL Server 2008 or later. (Microsoft.SqlServer.Management.UI.RSClient)
When I type the the new db engine (MSSQLSERVER03) over the old, I get an error: "TITLE: LAPTOP-999999\MSSQLSERVER03 cannot be found.The Reporting Services instance could not be found. (Microsoft.SqlServer.Management.UI.RSClient)
I also tried putting in the web address into the server name (suggested by DeanOC in a similar question).
Any direction on what to do next would be greatly appreciated!
thanks,
Ginger Burton
c
We have a Visual Studio Database Project that we are trying to move to Azure SQL Database. Some of our views use AT TIME ZONE which is supported in Azure SQL Database, but when I switch the database Target Platform to Microsoft Azure SQL Database in the project properties, it fails to build with error:
Error: SQL46010: Incorrect syntax near TIME.
I have connected directly to the database in Azure and I can use AT TIME ZONE, but I cannot create or publish a DACPAC file from my project.
This SO answer suggests switching the target to SQL Server 2016, but then you cannot deploy the DACPAC to Azure. It will give the error
A project which specifies SQL Server 2016 as the target platform cannot be published to Microsoft Azure SQL Database v12.
when publishing from Visual Studio or the command line with sqlpackage.exe. (Same with all targets).
This seems like a long-standing bug in Visual Studio Data Tools so others must have run into it. Does anyone have a workaround or suggestions?
I found the answer to this through another channel. This is a bug in Visual Studio 16.4 and the current preview of 16.5.
The Visual Studio 16.4 release removed support for Microsoft Azure SQL Database V11. In doing so, they removed the Project target for Microsoft Azure SQL Database V12, making the Microsoft Azure SQL Database the only option. The intention was for this new option to switch to targeting V12, but there is a bug and it still targets V11.
Until this is fixed in a future update of Visual Studio, the workaround is to manually edit the SQLPROJ file and change the line;
<DSP>Microsoft.Data.Tools.Schema.Sql.SqlAzureDatabaseSchemaProvider</DSP>
Adding in V12 to make it;
<DSP>Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider</DSP>
Save and reopen the solution. It now compiles and I can deploy to Azure.
This is the answer just to the second part of the question.
I had the same error while publishing .dacpac from free azure sql database to the one in basic plan.
A project which specifies SQL Server 2016 as the target platform cannot be published to Microsoft Azure SQL Database v12.
I figured that out by checking Allow incompatible platform in Advance setting of Publish Data-tier Application.
OK so I have a database project targeting SQL Azure Database V12
When running the sql into the exact azure database I want to target it runs in fine but via my database project I'm getting an error
The sql is
CREATE SEARCH PROPERTY LIST [spl_WorkersPropertyList];
The official documentation says this is supported...
https://learn.microsoft.com/en-us/sql/t-sql/statements/create-search-property-list-transact-sql?view=sql-server-2017
Anyone got any thoughts on what's going on? TIA
Please use Visual Studio 2017 and have the latest version of SSDT installed. Keep Target Profile as SQL Azure Database V12 or as SQL Server 2014 and deploying with the Ignore platform compatibility option.
I've downloaded SQL Server 2016 standard edition trial along with SSDT in order to test what one can do with a standard edition in SSIS, SSRS, and SSAS.
I also wanted to know whether standard version's SSISDB logging capabilities differs from the one in Enterprise. For this I wanted to create an SSISDB catalog under Integration Services Catalogs in SSMS.
When I try to do this, however, I get the error saying that
The catalog backup file 'C:\Program Files\Microsoft SQL Server\130\DTS\binn\SSISDBBackup.bak could not be accessed. Make sure the database file exists, and the SQL server service account is able to access it
From googling this issue it appears as this message shows up whenever someone doesn't have SSIS installed, but I have SSIS on the machine, I've even made a small Project and executed it from within SSIS without any issues just to verify.
I have set this up on localhost where I am the admin. Does anyone have any ideas why this won't work?
Regards,
Cenderze
To check if SSIS installed, open Sql Server Configuration Manager, in the SQL Server Services, is something like 'SQL Server Integration Services 13.0' running?
Experienced this error message on MS SQL Server 2017.
Resolved by launching MS SQL Server 2017 install media, added Integration Services feature.
After successful installation, when back into SSMS, right-click on Integration Services Catalog for Create Catalog... option.
You will be asked for an encryption password to create the new SSISDB.
Hope this helps!
I faced with this error when I used lower version of SSMS than SSIS. Check if you use proper version of SQL Management Studio.
You need to go back to the SQL Server installation and check the integration services checkbox.
The issue is because SQL Integration services is not installed properly with the existing SQL Server you are using.
you can check if SQL Integration services are installed or not by,
Opening --> SQL Server Configuration Manager--> SQL Server Services --> Check if "SQL Server Integeration Services is there"
if its there and if you still get the same issue try re-installing.
Else install the SQL Integration services to your existing SQL Server.
The detailed step to installation is given in this link : https://www.mssqltips.com/sqlservertip/6635/install-ssis/
hope this helps !!
I have a very fundamental and basic SQL question. Using Microsoft SQL Server Management Studio Express, how do I create my first Server? For that matter, how would I create it using any other required software tool?
I took a look at Sql Server Configuration Manager and I saw SQLEPRESS running as a SQL Server. But when I added that in to the start up widow for MSSM Studio Express, as the server name, it threw an error saying it cannot be found or does not exist. It seems that this is not the right kind of server.
To connect to the local instance of SQLEXPRESS, you will need localhost as the server name.
This is a fairly comprehensive guide on how to create a database once you have connected. All the steps won't apply to using SQL Express, but the gist of it is there.
In Object Explorer, connect to an instance of the SQL Server Database
Engine and then expand that instance.
Right-click Databases, and then
click New Database. In New Database, enter a database name.
To create
the database by accepting all default values, click OK; otherwise,
continue with the following optional steps.
Based on this comment:
Trying .\SQLEXPRESS in SQL Server Management Studio Express throws an error that says that "This version of Microsoft SQL Server Management Studio Express can only be used to connect to SQL Server 2005 servers". So this is the problem, I think.
.\SQLEXPRESS is the correct server name, but you have the wrong version of client tools (SQL Server Management Studio). To find out the version of SQL you are connecting to, there are a number of suggestions here: https://www.mssqltips.com/sqlservertip/1140/how-to-tell-what-sql-server-version-you-are-running/
But since you can't connect yet the easiest thing to do is go searching for sqlserver.exe, right click, properties, version. If you have multiple version you need take note of the folder that it's in and check the SQLExpress one. You can also check in services.
Once you've worked out the version, download and install just the management tools for that version.