Post reply

Migration from Oracle 10g to Sql sever 2005

  • June 8, 2011 at 3:03 am

    #251465

    Hello All,

    We have an Oracle 10G database which we use for our HRMS(People Soft). We are required to Create a .NET application with sql server as backend which uses the data from Same Oracle database.

    I want to migrate the oracle Database to Sql server & any data changes in oracle DB Should be reflected on a daily basis in my new SQL server Db,By means of scheduling or any other thing.

    Note:Only migration of tables along with data is required

    Kindly suggest.........

    Regards

    Umar

  • June 8, 2011 at 3:52 am

    #1335503

    You could use the Oracle migration assistant

    It's not as easy to use as it might seem and it hangs sometimes, but it kinda works.

    -- Gianluca Sartori

  • June 8, 2011 at 4:05 am

    #1335511

    Any idea on how to do it Using SSIS.

  • June 8, 2011 at 4:14 am

    #1335515

    Let me ask one question: why replicate the database to SQL Server if you can access the data from Oracle?

    I know, Oracle sucks. I hope there's a better reason for this choice. 😉

    -- Gianluca Sartori

  • June 8, 2011 at 4:56 am

    #1335532

    Reason to replicate is "Management Decision" may be some secuity concern for HRMS database ...

    Poor devlopers not left wd any Choice:doze:

  • June 8, 2011 at 5:59 am

    #1335563

    Managers know better. 😛

    I think you will have to create a package by hand or use the wizard.

    -- Gianluca Sartori

  • June 8, 2011 at 10:51 pm

    #1336030

    Any ideas on how to Schedule an SSIS package

  • June 13, 2011 at 3:18 am

    #1337631

    Why are you going for SQL Server 2005, which is now so old it is out of support? It would be better to look at SQL Server 2008 R2, the latest available on general release.

    Q4 or Q5 2011 should see the go-live of SQL Server Denali, and this has some major improvements to database mirroring (called HARDON) that IMHO will drive very fast adoption of Denali by SQL customers.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • June 14, 2011 at 2:58 am

    #1338221

    Umar, to schedule a SSIS package, simply create a new job in SQL Server and select Integrated Services Package as the type of code to run (vs the default TSQL). You will then be able to select the package that you want to schedule.

  • June 14, 2011 at 3:53 am

    #1338243

    Thanks William!!:-)

  • June 14, 2011 at 4:21 am

    #1338251

    I assumed that you have created all objects in SQL Server now you can use Linked Server in SQL Server and Database Link in Oracle to communicate these RDBMS each other

    then you have to write a Migration Process with the help of linked Server(SQL Server) or Database Link(Oracle)

    then you have to write an Integration Service for those tables which those are using DML in daily routine

    then you can use SQL Server agent service to schedule this integration service on required interval and in oracle you can create a direct job or you can use Enterprise Manager 10g to schedule this integration service

    you should install the Oracle Client on the Windows Server where SQL server is running and if you are using Oracle on Linux then you have to install Unix ODBC driver

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply