You work as the database administrator at Domain.com. All servers on the Domain.com network run Windows Server 2003 and all database servers run SQL Server 2005. The Domain.com network contains a database server named Certkiller -DB01 B01. Certkiller -DB01 hosts a database named CK_Sales that stores sales data for the company.
Domain.com recently acquired another company named Testlabs.com. Users in TestLabs.com also access the CK_Sales database on Certkiller -DB01. A Domain.com user reports that she often receives an error message when she accesses the CK_Sales database. You discover that an errant process is causing the error message. You need to terminate the errant process while minimizing the impact on users that are currently connected to the database. You identify the session ID (SPID) of the errant process as SPID 34.
What should you do next?
A.
Run the KILL SPID 34 Transact-SQL statement.
B.
Stop and restart the SQL Server Agent service.
C.
Locate the errant process in task manager and end the process tree.
D.
Run the KILL 34 Transact-SQL statement.
Explanation:
The errant process can be terminated by using the KILL statement and specifying the session ID as in KILL 34.
Incorrect Answers:
A: The KILL statement does not use the SPID clause, only the SPID number.
B: Stopping and restarting the SQL Server Agent service will affect all users that are connected to the database.
C: You cannot use Task Manager to terminate a SQL Server process. Task Manager terminates all processes associated with an application.
Reference:
Microsoft SQL Server 2005 Books Online (2006), Index: KILL statement