Re: Very long to to insert a row in an Oracle linked server
- From: Bob Hairgrove <NoSpamPlease@xxxxxxxx>
- Date: Sun, 08 Jul 2007 09:10:52 +0200
On Sat, 7 Jul 2007 19:08:01 -0700, Peter Jones
<PeterJones@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Bob,
Why is it necessary to go through SQL Server in the first place?
Well the app that supplied the data lives on a W2K3 server using a SQL
Server 2000 database and, when the client as for this data export facility,
is was 'easy' to integrate into the exisiting app by simply executing a SQL
Server 2000 stored proc that extracted the required info and simpy did an
insert against the Oracle database which was mapped as a linked server in SQL
Server 2000, e.g.
INSERT INTO Oracle..TMS.TMS_PACKINGLIST_DTL ( etc etc
I would be really interested in any suggestions re an alternate approach.
Cheers, Peter
OK ... does the stored procedure use bind variables and a prepared
statement for the insert, or does it issue 10 different queries with
everything in plain text? If you can, you should do it with a
prepared statement; that way, the server only needs to parse it once.
--
Bob Hairgrove
NoSpamPlease@xxxxxxxx
.
- References:
- Re: Very long to to insert a row in an Oracle linked server
- From: Bob Hairgrove
- Re: Very long to to insert a row in an Oracle linked server
- From: Bob Hairgrove
- Re: Very long to to insert a row in an Oracle linked server
- From: Bob Hairgrove
- Re: Very long to to insert a row in an Oracle linked server
- Prev by Date: Re: Very long to to insert a row in an Oracle linked server
- Next by Date: What is badmem ?
- Previous by thread: Re: Very long to to insert a row in an Oracle linked server
- Next by thread: What is badmem ?
- Index(es):
Relevant Pages
|