Post reply

Microsoft Connector for Oracle by Attunity

  • July 9, 2012 at 1:36 pm

    #263976

    Has anyone installed Microsoft Connector for Oracle by Attunity?

    For Attunity 32 do you also need to install the Oracle 32‐bit client as is stated below?

    Attunity 64‐bit connector (skip if not using SQL Enterprise edition)

    Attunity 32‐bit connector (skip if you don’t install the Oracle 32‐bit client)

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • July 9, 2012 at 11:09 pm

    #1510675

    according to Microsoft you do, if you want both to develop and to run SSIS packages on a 64-bit computer:

    http://msdn.microsoft.com/en-us/library/ee470675(v=sql.100).aspx

  • July 10, 2012 at 5:53 am

    #1510848

    prvmine (7/9/2012)

    according to Microsoft you do, if you want both to develop and to run SSIS packages on a 64-bit computer:

    http://msdn.microsoft.com/en-us/library/ee470675(v=sql.100).aspx

    I understand that you need both a 32 & 64 bit what I'm confused about is why you don't just have to install the Attunity product?

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • July 10, 2012 at 6:02 am

    #1510853

    Welsh Corgi (7/10/2012)

    prvmine (7/9/2012)

    according to Microsoft you do, if you want both to develop and to run SSIS packages on a 64-bit computer:

    http://msdn.microsoft.com/en-us/library/ee470675(v=sql.100).aspx

    I understand that you need both a 32 & 64 bit what I'm confused about is why you don't just have to install the Attunity product?

    maybe licensing? the same logic holds true for Office products; you can install the ACE drivers without having to install and tie up a ($600) license for microsoft office, if the only thing you need to do is Automation of word, excel or whatever.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • July 13, 2012 at 6:42 am

    #1512500

    Welsh Corgi (7/10/2012)

    prvmine (7/9/2012)

    according to Microsoft you do, if you want both to develop and to run SSIS packages on a 64-bit computer:

    http://msdn.microsoft.com/en-us/library/ee470675(v=sql.100).aspx

    I understand that you need both a 32 & 64 bit what I'm confused about is why you don't just have to install the Attunity product?

    There is a big difference the Attunity is nothing but a connector Microsoft reluctantly provided because we this poster included connected to Oracle with generic OLE DB connector back in SQL Server 2005. The Oracle client in the Microsoft platform is actually Oracle server with everything you need to develop for the Microsoft Platform without the ability to create a database, the reason Microsoft development requires TNS NAMES in the TNSNAMES.ORA file.

    Post again if you still need help.

    Kind regards,
    Gift Peddie

  • July 13, 2012 at 4:30 pm

    #1512737

    So far I'm good to go.

    I installed the 32 bit Oracle Client from the Command Line and that worked out and was able to creating an SSIS Package to load from Oracle to SQL Staging.

    I did not install the 64 bit version yet. Do you know if SQL Plus and ODBC are based on 64 bit?

    MVP Rob Kerr wrote a White Paper and said that from a performance perspective Attunity is a clear winner.

    Initially I could not get approval for the Enterprise version but I after an independent audit that I requested they sided with me and I got the approval for Enterprise Edition for the Data Warehouse Project.

    I waiting for the paperwork to go through so that I get a valid license so I can upgrade to the Enterprise Edition.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • July 13, 2012 at 6:34 pm

    #1512749

    I did not install the 64 bit version yet. Do you know if SQL Plus and ODBC are based on 64 bit?

    There are known issues with the x64 Oracle Client for Windows Vista and up because Microsoft changed the data access layer and Oracle did not create the x64 version quickly so in most cases both x86 and x64 are required. And I have not used SQL Plus for a while because both are not relevant to the Microsoft Platform development.

    MVP Rob Kerr wrote a White Paper and said that from a performance perspective Attunity is a clear winner.

    That just means Attunity was created for SSIS Fast Load which is faster than the generic OLE DB connector. You can connect to Oracle without the Attunity but you cannot do Oracle development in the Microsoft platform without the Oracle Client because it is required.

    Initially I could not get approval for the Enterprise version but I after an independent audit that I requested they sided with me and I got the approval for Enterprise Edition for the Data Warehouse Project.

    I waiting for the paperwork to go through so that I get a valid license so I can upgrade to the Enterprise Edition.

    You will not get good performance in a datawarehouse project with Standard edition.

    Kind regards,
    Gift Peddie

  • July 13, 2012 at 7:01 pm

    #1512754

    Gift Peddie (7/13/2012)

    I did not install the 64 bit version yet. Do you know if SQL Plus and ODBC are based on 64 bit?

    There are known issues with the x64 Oracle Client for Windows Vista and up because Microsoft changed the data access layer and Oracle did not create the x64 version quickly so in most cases both x86 and x64 are required. And I have not used SQL Plus for a while because both are not relevant to the Microsoft Platform development.

    I used SQL Plus as part of the to verification process.

    MVP Rob Kerr wrote a White Paper and said that from a performance perspective Attunity is a clear winner.

    That just means Attunity was created for SSIS Fast Load which is faster than the generic OLE DB connector. You can connect to Oracle without the Attunity but you cannot do Oracle development in the Microsoft platform without the Oracle Client because it is required.

    Initially I could not get approval for the Enterprise version but I after an independent audit that I requested they sided with me and I got the approval for Enterprise Edition for the Data Warehouse Project.

    I'm waiting for the paperwork to go through so that I get a valid license so I can upgrade to the Enterprise Edition.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • August 9, 2012 at 10:29 am

    #1523949

    Gift Peddie (7/13/2012)

    Welsh Corgi (7/10/2012)

    prvmine (7/9/2012)

    according to Microsoft you do, if you want both to develop and to run SSIS packages on a 64-bit computer:

    http://msdn.microsoft.com/en-us/library/ee470675(v=sql.100).aspx

    I understand that you need both a 32 & 64 bit what I'm confused about is why you don't just have to install the Attunity product?

    There is a big difference the Attunity is nothing but a connector Microsoft reluctantly provided because we this poster included connected to Oracle with generic OLE DB connector back in SQL Server 2005. The Oracle client in the Microsoft platform is actually Oracle server with everything you need to develop for the Microsoft Platform without the ability to create a database, the reason Microsoft development requires TNS NAMES in the TNSNAMES.ORA file.

    Post again if you still need help.

    You had posted a word document on installing the Oracle Client. I have the hard copy but the soft copy got corrupted.

    I could not find your original post.

    Could you please resend or repost?

    Thanks.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 9 posts - 1 through 8 (of 8 total)

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