List the current user list on given database
How to get a list of the users logged on to a specific database ? (instead of SP_WHO)
2003-04-09
339 reads
Lock and Connection Management
Correction to "drop/recreate objects" script.
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
222 reads
Drop and re-create all stored procedures or views
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,277 reads
SP to display locking users in tree format
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,162 reads
More Friendly version of sp_lock system sp.
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
1,056 reads
Locking Information - Simple SQL
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
688 reads
System Lock Snapshot
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
588 reads
Never use select into in transactions......
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,093 reads
sp_lock2 = sp_lock +shows database and object name
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
4,302 reads
Alert Procedure for Long-Running Job
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
4,009 reads
Blogs
Keeping Redshift System Table History Past 7 Days with S3 Tables
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
Updating the Data API Builder
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget
I am excited to host T-SQL Tuesday for the first time. I want to...
Forums
advice on ssrs version control
Hi we're a bit behind on versioning ssrs. I think we have over 1600...
Practical Ways to Approach SQL Server Problems and Case Studies
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Measuring Productivity
Comments posted to this topic are about the item Measuring Productivity
Question of the Day
Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers