deadlock/blocking in sql server

Hi,
My application using foxpro sometimes seems like hang and when connect to
sql server. I directly go to the sql server and use sp_lock to check whether
there is any thread is waiting and find out there is indeed one thread is
waiting and i use sp_who and can see one process got blocking. But these
things not happen in foxpro database. How i need to troubleshoot this
problem, what i can do so that i can prevent from blocking/deadlock. I have
a profiler and the profiler save the procedure. So, how i can check and
provent by using this profiler?
Thanks a lot.
regards,
florenceMaybe this article will help you:
http://www.sql-server-performance.com/sf_block_prevention.asp
--
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Florencelee" <florencelee@.visualsolutions.com.my> wrote in message
news:O6oIkQavEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi,
> My application using foxpro sometimes seems like hang and when connect
to
> sql server. I directly go to the sql server and use sp_lock to check
whether
> there is any thread is waiting and find out there is indeed one thread is
> waiting and i use sp_who and can see one process got blocking. But these
> things not happen in foxpro database. How i need to troubleshoot this
> problem, what i can do so that i can prevent from blocking/deadlock. I
have
> a profiler and the profiler save the procedure. So, how i can check and
> provent by using this profiler?
> Thanks a lot.
> regards,
> florence
>

deadlock/blocking in sql server

Hi,
My application using foxpro sometimes seems like hang and when connect to
sql server. I directly go to the sql server and use sp_lock to check whether
there is any thread is waiting and find out there is indeed one thread is
waiting and i use sp_who and can see one process got blocking. But these
things not happen in foxpro database. How i need to troubleshoot this
problem, what i can do so that i can prevent from blocking/deadlock. I have
a profiler and the profiler save the procedure. So, how i can check and
provent by using this profiler?
Thanks a lot.
regards,
florence
Maybe this article will help you:
http://www.sql-server-performance.co...prevention.asp
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
"Florencelee" <florencelee@.visualsolutions.com.my> wrote in message
news:O6oIkQavEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi,
> My application using foxpro sometimes seems like hang and when connect
to
> sql server. I directly go to the sql server and use sp_lock to check
whether
> there is any thread is waiting and find out there is indeed one thread is
> waiting and i use sp_who and can see one process got blocking. But these
> things not happen in foxpro database. How i need to troubleshoot this
> problem, what i can do so that i can prevent from blocking/deadlock. I
have
> a profiler and the profiler save the procedure. So, how i can check and
> provent by using this profiler?
> Thanks a lot.
> regards,
> florence
>
sql

deadlock/blocking in sql server

Hi,
My application using foxpro sometimes seems like hang and when connect to
sql server. I directly go to the sql server and use sp_lock to check whether
there is any thread is waiting and find out there is indeed one thread is
waiting and i use sp_who and can see one process got blocking. But these
things not happen in foxpro database. How i need to troubleshoot this
problem, what i can do so that i can prevent from blocking/deadlock. I have
a profiler and the profiler save the procedure. So, how i can check and
provent by using this profiler?
Thanks a lot.
regards,
florenceMaybe this article will help you:
http://www.sql-server-performance.c..._prevention.asp
Adam Machanic
SQL Server MVP
http://www.sqljunkies.com/weblog/amachanic
--
"Florencelee" <florencelee@.visualsolutions.com.my> wrote in message
news:O6oIkQavEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi,
> My application using foxpro sometimes seems like hang and when connect
to
> sql server. I directly go to the sql server and use sp_lock to check
whether
> there is any thread is waiting and find out there is indeed one thread is
> waiting and i use sp_who and can see one process got blocking. But these
> things not happen in foxpro database. How i need to troubleshoot this
> problem, what i can do so that i can prevent from blocking/deadlock. I
have
> a profiler and the profiler save the procedure. So, how i can check and
> provent by using this profiler?
> Thanks a lot.
> regards,
> florence
>

deadlock victim

h
im the below output from profiler..processes r getting deadlock and most of the time the below processes spid is causing blocking..but im unable to get procedure associated with that...
RPC Event 0 sp_executesql;
wot is sp_executesql;1 ?There are some trace falgs you can turn on to help resolve deadlocking
problems.
DBCC TRACEON (1204, 3605,-1)
will output info into your SQL Server ErrorLog.
--
HTH
Ryan Waight, MCDBA, MCSE
"sanjay" <anonymous@.discussions.microsoft.com> wrote in message
news:B1BF5BC8-8889-4054-9FDD-1FE3B52418B9@.microsoft.com...
> hi
> im the below output from profiler..processes r getting deadlock and most
of the time the below processes spid is causing blocking..but im unable to
get procedure associated with that...
> RPC Event 0 sp_executesql;1
> wot is sp_executesql;1 ?
>|||h
thnks for yr reply..but i failied to identify which the procedure associated with this...RPC Event 0 sp_executesql;
this "RPC Event 0 sp_executesql;1" im in getting profiler as deadlock processes

dead lock

Hi,
Yestoday I checked the SQL SERVER management information, it showed one
process blocked the others, the last TSQL command batch of the blocking
process was SET NOEXEC OFF, what's the reason that this process blocked
other processes, how to solve it?
ThanksHi,
I feel that the process mentioned by you may not be the probable case for
deadlock. COuld you activate the trace flag 1204 in server
to get more information on deadloak.
DBCC TRACEON(1204,-1)
This trace flag will put the information regarding the deadlock into sql
server error log for investigating the cause for deadlock.
Thanks
Hari
SQL Server MVP
"Taoge" <luxiaotao@.hotmail.com> wrote in message
news:u76Cq5MYFHA.1240@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Yestoday I checked the SQL SERVER management information, it showed one
> process blocked the others, the last TSQL command batch of the blocking
> process was SET NOEXEC OFF, what's the reason that this process blocked
> other processes, how to solve it?
> Thanks
>|||Actually, 1204 only forces a full scan debug of the deadlock chain. 3604
sends output to the client and 3605 sends output to the server error log.
However, at some point?I believe SP3?the 3605 flag was no longer required,
but it has gone back and forth a few times. So, I usually explicitly set
3605 as well.
Sincerely,
Anthony Thomas
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O7iETYPYFHA.3584@.TK2MSFTNGP12.phx.gbl...
Hi,
I feel that the process mentioned by you may not be the probable case for
deadlock. COuld you activate the trace flag 1204 in server
to get more information on deadloak.
DBCC TRACEON(1204,-1)
This trace flag will put the information regarding the deadlock into sql
server error log for investigating the cause for deadlock.
Thanks
Hari
SQL Server MVP
"Taoge" <luxiaotao@.hotmail.com> wrote in message
news:u76Cq5MYFHA.1240@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Yestoday I checked the SQL SERVER management information, it showed one
> process blocked the others, the last TSQL command batch of the blocking
> process was SET NOEXEC OFF, what's the reason that this process blocked
> other processes, how to solve it?
> Thanks
>