I have received the below errors while trying to migrate the MS SQL database to Azure SQL database.
Error Validating elements [Login_Name]: User:[Login_Name] has an unresolved reference to Login [AMD_Readonly]
The element User:[Login_Name] has property AuthenticationType set to a value that is not supported ij Microsoft Azure SQL Database v12.
Please guide me how to get rid from this issue.
With this given information, I suggest you to use Azure Data Migration Assistant (DMA) to detect compatibility issues that can impact database functionality in your new version of SQL Server or Azure SQL Database.
As you have given below error:
The element User:[Login_Name] has property AuthenticationType set to a
value that is not supported in Microsoft Azure SQL Database v12.
It seems like this is a feature in your source database which doesn't supported in Azure SQL Database, hence you are getting this error. To detect similar issues and recommendation, you can use DMA.
You can find the other DMA Capabilities to know more.
Check for SQL Server Compatibility Issues when Migrating to Azure using DMA
Related
I'm working to migrate an existing SQL Server 2008 database (on-premises) to Azure SQL. I'm able to generate a .dacpac file using Visual Studio. When I try to import the .dacpac file into Azure SQL, I get the following error:
Operation Name: Performs a database extension operation.
Error: The storage URI is not valid.
So far, I've verified that there are no spaces in the filename & the account does have permissions.
Any pointers to resolving this issue is appreciated.
Regards,
Rajesh
Some one get the same error which caused by the .bacpac file name contains a space. Please check it you have the same problem: Ref here: Error "The storage URI is not valid" when creating a new SQL Azure database from a bacpac.
I don't what your system is, if you are use windows system, please try to use the “deploy the database to SQL Azure” option from the SQL Server Management Studio (SSMS) to deploy the local SQL database to Azure. It's much easier.
Ref this tutorial: https://developer.relatude.com/deploying-a-sql-database-to-azure-with-sql-server-management-studio.
I am migrating on premises SQL server database to Azure PaaS SQL database using Data Migration Tool. I am not using Data Migration Service Instance mechanism to migrate the database as it would require VPN on the corporate network and I do not see any benefit doing that way in my case.
There is one error which I am stuck on and a bit confused. When migrating a stored procedure which use automation stored procedures, I get the following error:
When I run Alter procedure script directly on Azure SQL database , I get this error;
Reference to database and/or server name in 'MASTER..sp_OACreate' is not supported in this version of SQL Server.A few answers to similar question on stackoverflow suggest that Azure SQL does not support automation stored procedures but the Microsoft link has a green tick against Azure SQL which suggest it does; https://learn.microsoft.com/en-us/sql/relational-databases/stored-procedures/ole-automation-sample-script?view=sql-server-2017.
A snippet of the sp is:
Is it true that automation stored procedures are not supported in Azure SQL and if thats hte case then what is hte workaround apart from rewriting the sp?
SQL Azure prevents you from calling server resources. sp_OACreate attempts to create a reference to an OLE object on the server; that's simply not allowed on Azure SQL Database. So you will need to redesign your solution to move this type of logic in a middle-tier of some kind, such as a Web Role in Windows Azure.
I believed that I always got the latest version of SQL Server when creating a new Azure database from the Azure Portal. But that is not happening.
I always get sql Server version (12.0.2000.8) which is SQL 2014. I can't find other places to set a new compability level either.
Is there a problem with my subscription (pay as you go)??
Have any of you had the same experience as me, have you been able to solve it?
The reason I want SQL 2017 is that I want to publish SSIS packages to the SSISDB catalog, which is not possible on SQL 2014?
Hope any of you can help me out here
regards GEir
It's possible to use SSIS on DB engine 12 on Azure. Check out official documentation.
Additionally, you may upgrade your already-created azure databases by setting COMPATIBILITY_LEVEL modificator. Look into ALTER_TABLE documentation for examples.
Please note that although SQL Azure's engine share similar "engine api" as SQL Server 2014 (v12), those are not the same. What's more relevant in terms of supported features is maximum supported "Compatibility level".
I have this issue which I have asked about here
In all my programmatic attempts to fix the issue above, things like this are displayed in the messages box:
Reference to database and/or server name in
'master..sp_addsrvrolemember' is not supported in this version of SQL
Server.
How do I find the version of SQL Server,I am using? It seems nothing is supported by my version.
Is the issue can be that - I am not using SQL Server somehow? I am using Microsoft Azure to host my database. Does that make you use SQL Azure? In SSMS, in the Object Explorer, at the top where it says the server, it says gonskh1ou0.database.windows.net(SQL Server 13.0.201 - Amber). Amber is my user name, and is the administrator. SQL Server 13.0.201 is not in this list of SQL Server build numbers
Yes, you are using the Azure version of SQL Server, which does not support sp_addsrvrolemember.
(Do note that that stored procedure is deprecated and you should be using ALTER SERVER ROLE, which is supported at least in Azure SQL Data Warehouse's preview.)
The only way to run a full SQL Server is to create a VM and run it there yourself. The Azure version will never be the full version.
You are using Microsofts implementation of SQL server, the version number and name(Amber) supplied are indeed correct. Depending on the level of Azure account you are using, this server is usually configurable.
Microsoft Azures platform contains some very nice support and I would advise consulting directly with a rep. They have always been very helpful and quick to help in regards to configuration issues, even performing the configurations for you if required.
I cannot seem to browse the tables on my Azure SQL Server database from within Oracle SQL Developer (Version 4.1 - using jtds-1.3.1.jar plugin).
I can connect and perform all queries (inserts, selects, etc.), but when I try to expand it to view the tables, I see this error:
An error was encountered performing the requested operation:
Reference to database and/or server name in 'master..sysdatabases' is
not supported in this version of SQL Server.
Vendor code 40515
Note: I tried rolling SQL Server back to version 3, and I'm getting the same error.
Please advise. Thanks for your help!
We're not certified for Azure..there's a similar problem in SQL 2014. The way we're asking for a list of tables isn't valid in that version. Would require an enhancement request to support Azure for Oracle Database Migrations.