July 28, 2005 at 3:50 pm
I have a table that is being accessed by multiple procedures, now I have a certain procedure that needs to access this table that is being used by other procedures and I am timing out because of this. Does anyone know of a way/stategy to get around this problem and query the table? I'm not trying to modify anything, just query. I've thought of a view, but this is the same problem since the table will update the view and I still won't have access to the view. Is there a way to make a copy of the table at the instance my procedure needs to query the table, even if there are other procedures needing to use the table? There aren't millions of entries in my database, so there must be of a way to get around this issue; like Dell.
Thanks in advance
July 28, 2005 at 8:01 pm
I guess this is because your procedures are locking each other.
You can try to set the ISOLATION LEVEL or use with(nolock) hint in your select statement.
Leo
July 28, 2005 at 8:49 pm
The isolation level or lock hint will allow your query to run without timing out, however there sounds to be a more serious issue. Are there transactions that are staying open on the table for a great length of time? If so, are those dependent on the client to do something?
K. Brian Kelley
@kbriankelley
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply