Re: Updating Oracle database from SQL Server as linked table

On May 13, 3:07 am, Mladen Gogala <mgog...@xxxxxxxxx> wrote:
On Mon, 12 May 2008 18:46:31 -0700, Garrett  Fitzgerald wrote:
On May 12, 5:50 pm, "Terry Dykstra" <tddyks...@xxxxxxxxxxxx> wrote:
"Garrett Fitzgerald" <SarekOfVul...@xxxxxxxxx> wrote in message
I have a medical records system where parts live in Oracle and parts
live in SQL Server. I'm trying to inactivate a lot of patients who
haven't been seen since the conversion by updating them on the SQL
Server side and then updating the Oracle side to match. I'd like to
be able to use the following query:

UPDATE server..user.table
   SET OraField1 = 'I'
   WHERE OraField1 = 'A'
        AND OraField2 IN (
           SELECT SQLfield2
               FROM SQLTable
               WHERE SQLField1 = 1
           )

However, when I do this, I get an error saying that the field "was
reported to have a DBTYPE of 130 at compile time and 5 at run time".
... OpenQuery doesn't seem like it will do what I want, and I don't
want to accidentally inactivate everyone in the database...

OpenQuery is the only way you'll get around that dbtype error.  I've
found OpenQuery to work very well.

Ok, how do I do that? Would this be the correct syntax?

UPDATE OpenQuery(Server, 'select pid, orafield1, orafield2 from
oratable')
   SET OraField1 = 'I'
   WHERE OraField1 = 'A'
        AND OraField2 IN (
           SELECT SQLfield2
               FROM SQLTable
               WHERE SQLField1 = 1
           )

From Oracle side, in order to participate in a distributed transaction,
you would need the corresponding transparent gateway, a separately
licensed product. If and when you have that, something like this would
probably work:

with myview as (
     select pid, orafield1, orafield2,sqlfield2
     from oratable o,sqltable s
     where o.orafield2=s.sqlfield2 and
           orafield1 = 'A' and
           sqlfield1 = 1)
update myview set orafield='I'

That will work as long as the view contains the primary key of
the oracle table. Essentially, you need to do the update from the
Oracle side, not the SQL Server side, you need the GW software and license
and you can use the standard Oracle technique for "updating table A from
table B".

--
Mladen Gogalahttp://mgogala.freehostia.com- Hide quoted text -

- Show quoted text -

If this is being ran from the SQL Server side the Transparent Gateway
product would not be required.

If may also be possible to get around the ODBC error via the use of an
explict convert function in the code or if that does not work by
placing a view over the Oracle table that incudes the necessary
conversion. I think I have managed to work around one or two errors
using the above.

To run from the Oracle side instead of purchasing the Gateway product
you can try generic connectivity. This requires that you obtain
(purchase) and ODBC driver to SQL Server for the platform you run SQL
server on for all platforms except Windows where I believe the
necessary comes with the platform. I had this working on AIX for
Oracle version 8.1.7. With AIX I believe this feature is broke on ver
9 but it works on other platforms and a patch might have been
available. The developers choose to use a java program so we never
carried the HS forward after the initial tests.

The open query method should also work.

HTH -- Mark D Powell --

.

Relevant Pages

  • Re: Adding columns to SQL Server tables dynamically
    ... First of all reading tables rarely gets all the way to the "hard disk head". ... fragmentation in Sql Server or Oracle. ... nullable column and then updating each row. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Adding columns to SQL Server tables dynamically
    ... So would you recommend a production app to add columns through ado.net ... > fragmentation in Sql Server or Oracle. ... > nullable column and then updating each row. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: IOT, memory and transaction time
    ... easily generate it with DBMS_METADATA.GET_DDL if your verison of Oracle ... were pretty consistent no matter how big the table (this transaction ... FOREIGN KEY (versionNo) REFERENCES T_TRANSACTIONS, ... Oracle provides read consistency and SQL Server ...
    (comp.databases.oracle.misc)
  • Re: Database or store to handle 30 Mb/sec and 40,000 inserts/sec
    ... "Writers block readers and readers block writers in SQLServer. ... getting around this fundamental issue and because of it SQL Server ... admitted they can happen in Oracle, I guess Oracle should never been used ... isolation level but you will always disagree because you follow doctorine ...
    (comp.databases.oracle.server)
  • Re: IOT, memory and transaction time
    ... easily generate it with DBMS_METADATA.GET_DDL if your verison of Oracle ... If it was the update statement that references ... FOREIGN KEY (versionNo) REFERENCES T_TRANSACTIONS, ... There are however differences how both products deal with concurrency; in Oracle readers don't get blocked while this may happen in SQL Server. ...
    (comp.databases.oracle.misc)