Required to discover types defined in other schemas. Required to discover trigger definitions in other schemas. Required to discover PL/SQL for procedures, functions and packages in other schemas. Required to discover sequences in other schemas. Required to discover tables, views, materialized views and synonyms in other schemas. To obtain metadata for objects defined in other schemas, the account must have the following additional permissions: In most real-world scenarios there are cross-schema references between stored procedures and SSMA will need to be able to discover all referenced objects for a successful conversion. This will allow SSMA to load all objects in the schema owned by the connecting user. Required to query system dictionary tables (for example, SYS.MLOG$) in order to discover all objects. Required to connect (create a session) to the database. Required Oracle permissionsĪt minimum, the account that is used to connect to the Oracle database must have the following permissions: For more information, see the "Refreshing Oracle Metadata" section later in this topic. Instead, if you want to update the metadata in Oracle Metadata Explorer, you must manually update it. Metadata about the Oracle database is not automatically updated. When you reopen the project, you must reconnect if you want an active connection to the database. Your connection to the database stays active until you close the project. SSMA stores information about the database server, but does not store passwords. When you connect, SSMA obtains metadata about all Oracle schemas, and then displays it in the Oracle Metadata Explorer pane. To migrate Oracle databases to SQL Server, you must connect to the Oracle database that you want to migrate.
0 Comments
Leave a Reply. |