We were actually able to fix this, we ran dbcc flushprocindb([databaseId]),
and the query executed normally through ado.net. Maybe bad execution plan
or statistics?
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.