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.
Related
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
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".
We have a sql2k8 database that uses sp_xml_preparedocument, a master db system extended stored procedure, that needs to go to Azure. The migration tools (SSMS2016 wizard) give a validation error: SQL71501 that [dbo].[sp_xml_preparedocument] is a missing reference, when validating the export.
I can't see any way to reference the sp so it can be migrated. Intellisense always shows an error too.
Could you first verify that your code works fine on Azure SQL when you manually execute the scripts? When I execute queries with sp_xml_preparedocument from MSDN on my Azure SQL Database it works fine.
If your code works, then it is a problem in SSMS migration assistant, so in that case you should report bug on SQL Server Connect site, with some minimized repro script, so SQL Server team can fix it.
Use SQL Server 2016 Enterprise with Service Pack 1 (x64) . The SP1 should support Azure DB . The 2012 version of Sql server might do iT.
in my development environment we support the application both on MSSQL Server as well as Oracle. The database schema of both of these RDBMS are same.
while development we found that the developer made a mistake and forgot to change the oracle database for the last 1 yr. therfore the oracle script is quite behind in term of schema from SQL Server schema script.
now the question is how i can compare the two RDBMS systems to find the difference and make the oracle script updated
If there are no track log from which it's possible to find and reproduce all changes applied to SQL Server since first detected inconsistency with Oracle version, or that changes was applied, but only partially, you really need to compare objects presented in both databases.
In this case setup a link between databases on any side and use system dictionary views to compare table structures and other objects to find differences and, possible, to generate script for Oracle scheme rollup.
If you want to act from MS SQL Server side:
Install and configure Oracle Instant Client
Install Oracle ODAC
Follow Microsoft recomendations (64-bit version)
Connect as any user with dba role (or use same Oracle schema where object resides) to Oracle from MS SQL database
If you want to act from Oracle Server side:
Install and configure Oracle Database Gateway for SQL Server.
Create database link to MS SQL Server.
After successful configuration you may join Information schema views on SQL Server side with Data dictionary views on Oracle side to find differences.
Of course there are many troubles at this way like different data types, but it gives a chance to automate at least part of work.
Good day everyone!
I have a link server set up in SQL Server 2008 SP3 on Windows 7 64 for Oracle 11G Express.
I am using Oracle SQL Developer as a database application/Management system.
All is working well except for the long list of tables that's also in the Table tree.
There is a Filter function in SQL Developer, but I do not see the table APEX listed there.
Is there a way to configure SQL Server to that I see onle a specified table in the Link Server?
Here is an image of what I am referring to:
Thanks for the knowledge - you are making a great difference!
Guy
edit your account under security and go to user mapping untick master.
reconnect to sql server.
hope this helps.
or this link
http://msdn.microsoft.com/en-us/library/ms190644.aspx