You can move and change a Microsoft SQL Server database over to Oracle Autonomous Database 19c on Oracle Cloud Infrastructure (OCI) utilizing Oracle SQL Developer rendition 20.5 or higher. You can lead and deal with the whole data change and offline data migration with Oracle SQL Developer. The finishing time shifts and is, to, not set in stone by the size of source SQL Server database and the organization transmission capacity between the source and Oracle Cloud Autonomous Database. It is suggested that for better exchange insight, use Oracle Cloud Infrastructure Fast Connect between on-premises and Oracle Cloud.
This architecture utilizes Oracle Cloud Infrastructure File Storage to migrate data from an on-premises Microsoft SQL Server organization to an Oracle Autonomous Data Warehouse. The architecture is similar while relocating from another cloud service provide to Oracle Cloud. Oracle Cloud Infrastructure FastConnect or IPSec VPN gives private connectivity between your on-premises data centre or cloud service provider and Oracle Cloud Infrastructure (OCI).
After migrating the data to OCI, you can use the built-in machine learning, analytics, and AI tools to run complex queries across multiple data types, and build sophisticated analytical models.
- Data scientists can use Oracle Cloud Infrastructure Data Catalog to explore, discover, and analyze data.
- Business analysts can access and visualize information.
- Developers can build data-driven applications.
Required Services and Roles
- Oracle Cloud Infrastructure – Admin
- Oracle SQL Developer – db_datareader user on source Microsoft SQL Server Database system, mwrep user on target Oracle Database system
- Microsoft SQL Server – db_owner user
- Oracle Cloud Infrastructure File Storage – Admin
Provision Autonomous Database on OCI
Provision an Oracle Autonomous Database instance on Oracle Cloud Infrastructure according to size requirements of the source MS SQL Server database.
Perform the following prerequisite steps as necessary:
- Open the Oracle Cloud Infrastructure Console.
- From the left navigation menu click Oracle Database and then, depending on your workload click Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing. This example uses Autonomous Data Warehouse.
- Choose your region.
- Choose your Compartment.
- Click Create Autonomous Database.
- Provide basic information for the Autonomous Database.
- Choose a compartment.
- Display name: Specify a user-friendly description or other information that helps you easily identify the resource. The display name does not have to be unique.
- Choose a workload type. To create Autonomous Data Warehouse instance, select Data Warehousefrom the choices.
- Choose a deployment type.
- Select Shared Infrastructureto create your instance on Shared Exadata Infrastructure.
- Configure the database.
- Always Free: Select to show Always Free configuration options.
- Choose database version: Select the database version. The available database version is 19c.
- With Always Free selected, the available database versions are: 19c and 21c.
- OCPU Count: Specify the number of CPU cores for your database.
- Storage (TB): Specify the storage you wish to make available to your database, in terabytes.
- Auto Scaling: By default auto scaling is enabled to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand. If you do not want to use auto scaling then deselect this option to disable auto scaling.
- Create administrator credentials. Set the password for the Autonomous Data Warehouse Admin user.
- Username: This is a read only field.
- Password: Set the password for the Autonomous Data Warehouse Admin user.
- Confirm password: Enter the same password again to confirm your new password.
- Choose network access.
- Allow secure access from everywhere: By default all secure connections are allowed from everywhere. To restrict access configure an access control list (ACL). To add an ACL for the Autonomous Database, select Configure access control rules.
- Virtual cloud network: This option assigns a private endpoint, private IP and hostname, to your database inside your VCN. Specify this option if you want your database to be accessible only within your VCN using a private endpoint; this option allows you to restrict access to an Autonomous Data Warehouse database.
- Choose a license type
- Bring Your Own License
My organization already owns Oracle Database software licenses. Bring my existing database software licenses to the database cloud service.
- License Included
Subscribe to new database software licenses and the database cloud service.