You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ssma/oracle/connecting-to-oracle-database-oracletosql.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Your connection to the database stays active until you close the project. When y
23
23
24
24
Metadata about the Oracle database is not automatically updated. Instead, if you want to update the metadata in Oracle Metadata Explorer, you must manually update it. For more information, see the "Refreshing Oracle Metadata" section later in this topic.
25
25
26
-
## Required Oracle Permissions
26
+
## Required Oracle permissions
27
27
28
28
At minimum, the account that is used to connect to the Oracle database must have the following permissions:
29
29
@@ -79,7 +79,7 @@ Some of the SSMA features require additional permissions. For instance, if you w
79
79
> [!NOTE]
80
80
> This is a generic set of permissions required for SSMA to operate properly. If you want to narrow down the scope of your migration to a subset of schemas you can do so by granting above permissions to the limited set of objects, instead of `ALL`. While possible, it might be very hard to correctly identify all dependencies, thus preventing SSMA from functioning properly. It is highly recommended to stick to the generic set as defined above to eliminate any potential permission issues during migration process.
81
81
82
-
## Establishing a Connection to Oracle
82
+
## Establishing a connection to Oracle
83
83
84
84
When you connect to a database, SSMA reads the database metadata, and then adds this metadata to the project file. This metadata is used by SSMA when it converts objects to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] syntax, and when it migrates data to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. You can browse this metadata in the Oracle Metadata Explorer pane and review properties of individual database objects.
85
85
@@ -123,7 +123,7 @@ When you connect to a database, SSMA reads the database metadata, and then adds
123
123
124
124
Your connection to the database server stays active until you close the project. When you reopen the project, you must reconnect if you want an active connection to the database. You can work offline until you want to update metadata, load database objects into [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], and migrate data.
125
125
126
-
## Refreshing Oracle Metadata
126
+
## Refreshing Oracle metadata
127
127
128
128
Metadata about the Oracle database is not automatically refreshed. The metadata in Oracle Metadata Explorer is a snapshot of the metadata when you first connected, or the last time that you manually refreshed metadata. You can manually update metadata for all schemas, a single schema, or individual database objects.
129
129
@@ -146,10 +146,10 @@ Metadata about the Oracle database is not automatically refreshed. The metadata
0 commit comments