DB2 linked server issues

I have a DB2 linked server using DB2OLEDB from MS. the DB2 table does not have journaling enabled, so all of my data creation and update statements are failing when using OpenQuery. Is there a way to get my data mod statements to execute on DB2 without requiring journaling? I have tried using ODBC and setting the Commit Level to none, but it appears that SQL server overrides that setting when connecting through the Linked Server. Any ideas?

Have you tried using

a Control Panel ODBC System DSN entry as your data source? This old school

connection technique fixed my numerous db2 linked server problems. I suspect

there is a bug in the IBM drivers that goes away when you configure the

connection like this.

It should also fix

your settings override problem and give you access to even more settings to tinker

with!

Thanks,
Greg Van Mullem

|||

we have tried using an ODBC DSN as the source for the Linked Server, but it still has the same problems. Somehow SQL Server seems to force the "transaction log/journaling" upon the ODBC source as well.

|||If you are running the Developer or Enterprise Edition

of SQL Server you could try this feature pack download from Microsoft.

Unfortunately, it does not work with SQL Standard Edition so I have not

been able to try it.

Microsoft

OLEDB Provider for DB2

Thanks,
Greg Van Mullem|||Have you tried the new EXEC AT syntax with linked server in SQL Server 2005?