I have built half dozen DTSs. They are running fine on my machine, but failed to finish on the server. So far this is too familiar story, but this time, the following error message baffled our dba and me.
“Query cannot be updated because it contains no searchable columns to use as a key”.
I even found an article from the MSDN KB.
http://support.microsoft.com/default...b;en-us;326166

It has something to do with using query to update a cursor while the cursor doesn’t contain any key column in it. And it is a by design behavior of the OLE DB Provider for ODBC driver.

On our case, I did not manipulate cursor/query whatsoever. It is a strict copy table from SQL2k to DB2 through Client Access ODBC Driver. All tables have primary keys. Both connections (DSNs) to the source and the destination seem good. At the server machine’s EM, I can preview the data from the source, as well as seeing the table field name from the destination. And the DTS is executed manually instead of as a scheduled job. The error showed up at the lat step of the package.

Anybody have any idea? Thanks!

The KB article also mentions the data types of columns as well. Is this an
issue ?


--


Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org




"Hong" <anonymous (AT) discussions (DOT) microsoft.com> wrote

time, the following error message baffled our dba and me.
of the OLE DB Provider for ODBC driver.
have primary keys. Both connections (DSNs) to the source and the destination
seem good. At the server machine's EM, I can preview the data from the
source, as well as seeing the table field name from the destination. And the
DTS is executed manually instead of as a scheduled job. The error showed up
at the lat step of the package.

I really don't know, but I think I included every columns
from the source, among them there is a primary key.
The difference between my machine and the server is that I
have an older version of Client Access. I am going to
compare them and search IBM site for help.