Re: **kill process**

M
http://www.sql-server-performance.com/reducing_locks.asp



"M" <rez1824@xxxxxxxxxxx> wrote in message
news:op.tf7puxfcn9ig5y@xxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi

In SQL 2000, sometimes it takes a long time to fetch data from a very
simple table that in normal cicumestances I can get the information in a
glance. and when I take look at
(enterprise manager->management->current activity->locks/process id)
I'll find some spids with red icon in blocking mode, so by right clicking
and killing the process I can get ride of them.
and I 've found in lock/objects when I have a view or procedure which is
locked all its tables are locked too.
I want to know when this problem occure and why? how can I prevent any
locking?
or how can I be informed when a lock object happened to go and kill
it?(should I accidently discover it?)

any help on this issue would be appreciated.


.

Relevant Pages

  • **kill process**
    ... In SQL 2000, sometimes it takes a long time to fetch data from a very simple table that in normal cicumestances I can get the information in a glance. ... I want to know when this problem occure and why? ...
    (microsoft.public.sqlserver.security)
  • Access Query - Between Operator showing additional data
    ... In one report i am using between operator in SQL to fetch data from access database. ...
    (microsoft.public.access.queries)