We had a stored procedure with one section that populates a single variable in the SP from a query to a MSAccess database MDB file via a linked server. It was running from SQL Server MSDE 2000 and it was fast on an XP system.
We transferred to a SQL Server 2012 database on a 32bit Win 7 machine and the same SP will time out before returning a simple result. Code calls a SP and within that SP is a call to another SP where it shows the timeout error message. I can run the exact same SP in SSMS on a Win 7 box hitting the very database where the error occurs during the program code execution and it returns results in less than one second.
I've heard folks talk about this being a known problem. Does anyone have a workaround to resolve this issue?
TIA
Harry