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....

КОМЕНТАРІ •

  • @BenjaminGSlade
    @BenjaminGSlade 6 місяців тому

    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?

  • @SujitPatil-s4b
    @SujitPatil-s4b 3 місяці тому

    Can we remove the username from the table name which created while migration ?

  • @MarphiLeu
    @MarphiLeu Рік тому

    I can do migration process by SSMA manually, but i need to do periodically ( as scheduled job ) any idea ?

    • @HemantKChitale
      @HemantKChitale  Рік тому

      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.

  • @kiranyasa2000
    @kiranyasa2000 3 роки тому +1

    Thanks

  • @AKsharma_NL
    @AKsharma_NL 2 роки тому

    you did not rant "convert schema" .. may be because you manually created the object in sql server db ?

    • @HemantKChitale
      @HemantKChitale  2 роки тому

      The DDLs were generated by the Migration Assistant . So I didn't have to "convert schema" (not sure what you mean by "convert schema")

  • @Mau_N_Mom
    @Mau_N_Mom 2 роки тому

    Thank you for proper explanation... I have 1 questions, can you guide on oracle sequence migration?

    • @HemantKChitale
      @HemantKChitale  2 роки тому

      I'd suggest configuring the column as Identity Column so that SQL Server generates the values.

  • @abrahammathew9783
    @abrahammathew9783 3 роки тому

    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..

    • @HemantKChitale
      @HemantKChitale  2 роки тому

      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

  • @Dorairaj-r3w
    @Dorairaj-r3w Рік тому

    Does Migration assistant can only be installed in SQL Server machine

    • @HemantKChitale
      @HemantKChitale  Рік тому

      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.

  • @DesChew
    @DesChew 2 роки тому

    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.

    • @HemantKChitale
      @HemantKChitale  2 роки тому

      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.

  • @1-minuteshorts214
    @1-minuteshorts214 Рік тому

    Is there a way to schedule this SSMA process ?

    • @MarphiLeu
      @MarphiLeu Рік тому

      Any solution did you get do as schedule job ?

    • @HemantKChitale
      @HemantKChitale  Рік тому

      I'd suggest extracting the generated scripts, adding DROP and DELETE statements and scheduling through an external Scheduler (VisualCron and PowerShell) or BMC

    • @HemantKChitale
      @HemantKChitale  Рік тому

      I'd suggest extracting the generated scripts, adding DROP and DELETE statements and scheduling through an external Scheduler (VisualCron and PowerShell) or BMC