what is the proper way to close a non responding task?
Hi experts,
I have an access FE application that is linked to 50% access tables and 50% sql tables.
I run sometimes in situations where I have a non responding running query.
very often its joining Access and SQL tables in one query.
What is the safest way of stopping it?
a-at the clients pc call task manager and end the access non responding app.
b-from SQL SSMS kill that transaction.
I have an access FE application that is linked to 50% access tables and 50% sql tables.
I run sometimes in situations where I have a non responding running query.
very often its joining Access and SQL tables in one query.
What is the safest way of stopping it?
a-at the clients pc call task manager and end the access non responding app.
b-from SQL SSMS kill that transaction.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just note that, In newer versions of Access, "Not Responding" often means that the operation is just taking a long time to run.
How long are you waiting till you try to kill the app?
Can you post the SQL behind the query?
Sometimes the SQL is too complex, ...or contains elements that slow down the processing (Aggregate functions, wildcards, nesting, sub queries, ...etc)
JeffCoachman
How long are you waiting till you try to kill the app?
Can you post the SQL behind the query?
Sometimes the SQL is too complex, ...or contains elements that slow down the processing (Aggregate functions, wildcards, nesting, sub queries, ...etc)
JeffCoachman
If you don't encapsulate the query update in a transaction, you will end up compromising the data integrity.
ASKER
Hi,
Sql attached, It takes a while (could take few minutes) and I was given the task to expedite..
however, as mentioned after I pressed contrl+break I waited about 20 minutes before killing it.
sql.txt
Sql attached, It takes a while (could take few minutes) and I was given the task to expedite..
however, as mentioned after I pressed contrl+break I waited about 20 minutes before killing it.
sql.txt
ASKER
@MacroShadow,
As you can see from SQL attached, this is a read only query, not updatable, so is this risky to be killed?
As you can see from SQL attached, this is a read only query, not updatable, so is this risky to be killed?
Considerably less risky, but there still is risk of corruption to the FE, which is even less of concern because it can be easily replaced.
ASKER
Hi Experts,
While working on expedite this query I found out something marvelous..
Instead of joining them all at once, I split it into 2 queries, the first took all data that comes from sql tables, and the second takes the results of first query and join them with the access tables.
The result is incredible...
It takes seconds instead of few minutes!!!
Now I can enhance it even further by having the first query be converted to a pass-through query or save it as a view in sql and link it as it would be a table.
While working on expedite this query I found out something marvelous..
Instead of joining them all at once, I split it into 2 queries, the first took all data that comes from sql tables, and the second takes the results of first query and join them with the access tables.
The result is incredible...
It takes seconds instead of few minutes!!!
Now I can enhance it even further by having the first query be converted to a pass-through query or save it as a view in sql and link it as it would be a table.
Seems like you're problem is solved <grin>
ASKER
@MacroShadow:
Thanks, Indeed this was the answer for my original question, I just got taken by other topic that should really be posted in another thread.
Thanks, Indeed this was the answer for my original question, I just got taken by other topic that should really be posted in another thread.
ASKER
How about the data stored in Access tables, does it makes a difference?
The last incident I had was when after a while, I pressed Contrl+Break, is that something that should be avoided, as it looks like Access does not transfer the command properly to SQL?