SQL Server Migration Assistant for Oracle
Вставка
- Опубліковано 9 лют 2025
- A demonstration of the SQL Server Migration Assistant for Oracle.
It also shows the stored procedure code, code for views and datatypes. So you can compare your Oracle Code and definitions with those that will be created in SQL Server.
The SQL Server Migration Assistant is available at techcommunity....
Nice video. Thanks. One thing I'd be curious about is, what if you have a large schema with several errors that require manual modification at the destination? What's the process flow for that? Specifically, can you run the migration, then in the Migration Assistant, go to each problem object and manually fix it in the destination?
Can we remove the username from the table name which created while migration ?
I can do migration process by SSMA manually, but i need to do periodically ( as scheduled job ) any idea ?
I am not aware of an in-built scheduler. However you could consider extracting the scripts, adding any DROP or DELETE statements as required, and scheduling them through a job scheduler (VisualCron and PowerShell) or BMC.
Thanks
Welcome
you did not rant "convert schema" .. may be because you manually created the object in sql server db ?
The DDLs were generated by the Migration Assistant . So I didn't have to "convert schema" (not sure what you mean by "convert schema")
Thank you for proper explanation... I have 1 questions, can you guide on oracle sequence migration?
I'd suggest configuring the column as Identity Column so that SQL Server generates the values.
Hi , Thanks for the video, its helping me with migration. I have a query what is Equivalent of Oracles sys_context ('USERENV', 'Client_Identifier') in SQL Server. I am getting errors w.r.t same after schema conversion..
I'm sorry, I don't know an equivalent. The DBA can query sys.dm_exec_connections to identify connections but if your requirement is for a non-DBA session to identify client_identifier you might try working with this view
Does Migration assistant can only be installed in SQL Server machine
Well, it has to be on a Windows Server. If you are thinking of an installation connecting to multiple SQL Server instances, you would be able to define a connection to each instance.
Hi, can you do a video showing some error with the Oracle number datatype conversion? By default SQL server will set as float[53]. How can we change to numeric? I try that in project settings. But the SSMA doesn't allow me to migrate successfully.
You could ALTER TABLE MODIFY the column in Oracle to set the correct Precision and Scale before you run the Migration Assistant.
OR
You could modify the generated SQL Server DDL statements.
Is there a way to schedule this SSMA process ?
Any solution did you get do as schedule job ?
I'd suggest extracting the generated scripts, adding DROP and DELETE statements and scheduling through an external Scheduler (VisualCron and PowerShell) or BMC
I'd suggest extracting the generated scripts, adding DROP and DELETE statements and scheduling through an external Scheduler (VisualCron and PowerShell) or BMC