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:
2003-02-06
200 reads
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 […]
2003-02-05
1,164 reads
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 […]
2002-08-19
2,038 reads
This SQL Server stored procedure generates more readable output from the system sp_lock procedureinstead of getting object ids and session ids it returns the object name and user name
2002-07-10
799 reads
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!
2002-07-10
655 reads
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 […]
2002-06-14
568 reads
If select into clause is used into transactions till the transaction commits sysobjects table can not acceses directly.It can be accessed only with 'nolock' hint.
2002-06-07
1,074 reads
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 […]
2002-06-06
3,098 reads
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 […]
2002-01-15
3,924 reads
When executed against a database in which blocking occur, below script will report lockType, Object waited for and current Wait times. The script requires access to master..systables. The script queries syslockInfo (as does sp_lock), but further joins sysprocesses with an interpretation of waitresource matching SQL Server 7.0 and SQL Server 2000.
2002-01-14
2,525 reads
By Steve Jones
I started to add a daily coping tip to the SQLServerCentral newsletter and to...
Over the past couple of years, I’ve developed several tools that I’ve been using...
/* Author:Brahmanand Shukla (SQLServerCarpenter.com) Date:27-May-2022 Purpose:To get all the stored procedures and triggers missing the use of...
Can someone let me know why I'm not able to use CAST method to...
If i deploy a standalone Azure VM running SQL Server into an availavility zone;...
So I have inherited an older SQL 2014 Server and have been working on...
Ask SSC