Search
InstantDoc ID
GO

Browse By: Author | Issue

August 19, 2003 03:19 PM

Sysprocesses in SP3

SQL Server 2000 SP3 enhancements make troubleshooting easier
Rating: (0)
Kalen Delaney
SQL Server Magazine
InstantDoc ID #39664
In my previous two columns, I told you about several system tables that I find most useful and examined some columns in one of my favorite system tables: sysprocesses. I also described how you can use columns from sysprocesses to troubleshoot locking and blocking problems. (See "Inside Sysprocesses," July 2003, InstantDoc ID 38674, and "Track Down Troublemakers," August 2003, InstantDoc ID 39453, for details.) This month, I finish discussing the usefulness of sysprocesses by looking at some columns that Microsoft added to that table in SQL Server 2000 Service Pack 3 (SP3).

Mic...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Compare Member Benefits

Add a Comment

I've tried this solution, and have not had any success. The problem stems from the SELECT @Handle statement. I checked sysprocesses and located TWO or more rows for each spid. One spid generally has a sql_handle. The others have zeros. If I enter the sql_handle that is not zero, I still get the Handle not found in cache statement, and the statements I've tried are definitely not insignificant so they should be in cache. I'd really like to use this solution, but I think I need more information?

Lezza 9/23/2003 7:34:16 AM

You must log on before posting a comment.

Are you a new visitor? Register Here

© 2010 Penton Media, Inc.

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.