odbc vs oledb for odbc - performance anxiety
- From: bsheeres@xxxxxxxxx
- Date: 28 Nov 2005 12:40:51 -0800
What does work:
Uing access and odbc (informix-cli 2.5 drivers) update data in a linked
informix table. The performance is quite good, even when joining a
local table to the linked table.
What does *not* work:
Using sql server 2k and oledb for odbc (same drivers) update data in a
table in the linked informix server. The performance is aweful. This
setup takes almost 30 minutes to do the same thing the access setup
does in a few seconds. I've tried using 4 part fully qualified naming,
openquery, openrowset, dynamic slq nothing seems to work well.
What I have noticed in the Q/A is that a estimated execution plan for a
*select* statement against the linked server (with a join on a local
table) will include a where clause (where c.upcno=?) in the remote
query, while the estimated execution plan for an *update* statement has
no where clause. Curious.
Can anybody explain whats going on and how I can fix the problem?
TIA
Brian Sheeres
.
- Prev by Date: tempdb problem
- Next by Date: Re: NewBie, SQLAllocHandle only works on Win2003Server.
- Previous by thread: tempdb problem
- Next by thread: .net odbc provider, sql2005, linkedserver
- Index(es):
Relevant Pages
|
Loading
