July 13, 2007 at 10:42 am
Hi guys,
I currently have a server running SQL Server 2005 Enterprise Edition. I've installed Microsoft's OLE DB Provider for DB2 and am using a linked server within my SQL server environment to access data from a DB2 database residing on another machine.
I've found that data access is incredibly slow, this problem is becoming worse over time as the tables in DB2 grow with more data (I don't think it sees the indexes). For instance, a query directly on the DB2 box takes a couple of seconds to run and the exact same query returning 1 row takes about 23 minutes on my SQL box!
On top of this I'm receiving "insufficient memory" bugs on a daily basis within the SQL Server environment. The box is up to date with the latest service packs... The out of memory error I feel is being caused by the linked server, just a guess though.
Has anyone else had the same issues with this provider?
I've reached the point whereby I feel like scrapping the provider completely on the SQL side and having the DB2 guys develop all the integration from their side as they're not having any of the same problems with there IBM provider connecting to SQL Server.
I don't feel the MS has done a very good job in terms of developing this software... 🙁
Your assistance would be greatly appreciated.
July 16, 2007 at 2:20 am
Move to latest Service pack for SQL Server 2005.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 16, 2007 at 8:37 am
The latest Service Pack would not make a difference as I noticed the same thing. Performance wasn't as bad as what you've mentioned during my tests but the OLE for DB2 driver is a lot less efficient than the ODBC driver (especially if the DB2 driver is on a 64 bit machine for some strange reason). If you don't have a 64 bit SQL server, I would suggest you use the ODBC driver. That is the most efficient one I've found in my testing.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply