Home > Archive > MS SQL Server ODBC > November 2005 > odbc vs oledb for odbc - performance anxiety









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author odbc vs oledb for odbc - performance anxiety
bsheeres@gmail.com

2005-11-28, 8:23 pm

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

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com