I have an extremely strange problem.
I have an access database front end linked to a sql server backend via ODBC .
The sql server was a replicated server of 4 up to 27/03/14 and then 3 were decommissioned leaving just the one server.
The issue I'm having is if I run a pass through query in the access client to just one table using a date field between and combination of dates it works fine.
If I then add another table to this query (using whatever joins) using any start date on or before 27/03/14 to any future date it runs in seconds
But if I change the start date to any date after the 28/03/14 to a future date it then can take minutes to run. This also still happens if I use a different date field. For each end date I increase the slower it takes to run.
Therefore, something must have occurred during the decommissioning of the old three replicated servers. (no users were in the database at that time it was changed).
This issue is also happening on another data table in the database.
Im stumped ... please help
I have an access database front end linked to a sql server backend via ODBC .
The sql server was a replicated server of 4 up to 27/03/14 and then 3 were decommissioned leaving just the one server.
The issue I'm having is if I run a pass through query in the access client to just one table using a date field between and combination of dates it works fine.
If I then add another table to this query (using whatever joins) using any start date on or before 27/03/14 to any future date it runs in seconds
But if I change the start date to any date after the 28/03/14 to a future date it then can take minutes to run. This also still happens if I use a different date field. For each end date I increase the slower it takes to run.
Therefore, something must have occurred during the decommissioning of the old three replicated servers. (no users were in the database at that time it was changed).
This issue is also happening on another data table in the database.
Im stumped ... please help
