Killing the job is your first alternative, then redesign your procedures
and/or tables. Locks are integral to the SQL Server engine and they are not
something you can play with. You can provide hints in your procedures to
reduce locking in the first place. For instance, you should always use WITH
(NOLOCK) if you are simply reading from a table and dirty reads are OK. You
must also have your tables organised to support your code, or vice-versa,
with judicious use of indexes (clustered indexes are VERY useful). At all
costs, avoid table scans. Here is evidence that writing code in SQL is not
just a matter of writing code.
-----Original Message-----
From: Chaohua_Wang
[mailto:mssqldba-ezmlmshield-x17769888.[Email address protected]
Sent: Thursday, 29 November 2007 6:47 AM
To: LazyDBA Discussion
Subject: Re: Urgent help required : Facings DB locking problem in sql server
2000
Could you kill one of jobs using
KILL spid#
Moazam <mssqldba-ezmlmshield-x91822307.[Email address protected]
11/28/2007 11:22 AM
To
"LazyDBA Discussion" <[Email address protected] cc
Subject
Urgent help required : Facings DB locking problem in sql server 2000
Hello experts
Facings DB locking problem in sql server 2000 Is there any way to release
lock on db objects by there Name
i have two set of stored procedure when i run those stored procedure in
different batches they work fine but i have to call those stored procedure
in one batch by set of triggers i just want to know that is there any way to
release some table from lock say release lock "Table name "
Thanks & Regards,
Moazam Shaharan
Software Engineer.
NetSol Technologies Inc.
NetSol IT Village
NetSol Avenue, Ghazi Road
Lahore Cantt. 54792, Pakistan.
Tel: +92 42 111 44 88 00 (Ext. 510)
Mob: +92 300 6848200
Fax: +92 42 572 6740
DISCLAIMER: This e-mail and any file transmitted with it is confidential and
intended solely for the use of the addressee. If you are not the intended
recipient, you are notified that disclosing, copying, distributing or taking
any action regarding the contents of this information is strictly
prohibited. If you have received this email in error, please return the
original to the sender and destroy the same immediately. Any views or
opinions presented in this email are solely those of the author and do not
necessarily represent those of the company.
WARNING: The recipient should check this email and any attachment for the
presence of viruses. Although the company has taken reasonable precautions
to ensure no viruses are present in this email, the company does not accept
responsibility for any loss or damage arising from the use of this email or
attachment.
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a dba
job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com To
unsubscribe: http://www.lazydba.com/unsubscribe.html
**********
The information contained in this communication is confidential, private,
proprietary, or otherwise privileged and is intended only for the use of the
addressee. Unauthorized use, disclosure, distribution or copying is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify the sender immediately at
(312)653-6000 in Illinois; (800)835-8699 in New Mexico; (918)560-3500 in
Oklahoma; or (972)766-6900 in Texas.
**********
---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a dba
job: http://jobs.lazydba.com To subscribe : http://www.LazyDBA.com To
unsubscribe: http://www.lazydba.com/unsubscribe.html
MS Sql Server LazyDBA home page