Regarding the recent script I submitted (dropping/recreating all procedures/views) - I made an important oversight. I neglected to add a CASE statement in order to make sure that the appropriate type of object was being referenced in the DROP statement.Below is the corrected script:
There are times when you may need to drop and re-create all stored procedures and/or views in your database. For example, in cases where procedures or views are causing blocked locks or other performance problems, a recent article (http://www.sswug.org/see.asp?s=1166&id=13448) suggested dropping/re-creating procedures and views after a service pack has been installed. The installation of a […]
This SP will give a listing of users blocking and being blocked in a tree formation (similar to explorer tree list). It uses a User defined function that recurses through the locking information gathered from sysprocesses. The listing only shows the Hostname (username) and the SPID.First create the User Defined Function (Part One) then create […]
Here's a simple SQL to give you locking information.The SQL tells you what resource type you are using, the object name, lock request mode, lock status, and also the calling program's name.And all this from a simple query on sysprocesses, and syslockinfo!
This script captures the current system lock in a temp table, then builds a temp translation table for database and object id by iterating through all of the databases. It then produces a report by joining the two tables.For better performance, you could make the translation table perminante and only update it when you are […]
sp_lock2 is similar to sp_lock, except that it displays the database name, object name and index name instead of the ids. It accepts no parameters unlike the sp_lock procedure which can take an optional spid parameter. The basis for the main query which queries the system tables for lock info was taken from the sp_lock […]
For jobs that run periodically and should take only a short time to run, a DBA may want to know when the job has been running for an excessive time. In this case, just checking to see IF the job is running won't do; the ability to make sure that it hasn't been running for […]