>I figured it out. It turned out to be a setting in the ODBC connection settings. There is a checkbox called "Bind NUMBER as FLOAT". I select that checkbox - and now all is working nice and speedy again. From what I understand it's a glitch caused by using numbers as primary keys - and clicking this checkbox in the ODBC connection manager for Oracle fixes it.

Interesting. In my case I found that all parameters were send as float to SQL Server while the actual columns were numeric(17,0) [Should have used BigInt, but it's another story]. Anyway, now I manually do cast(?parName as decimal(17,0)) to make sure I pass parameter of the correct type.