| title | srv_got_attention (Extended Stored Procedure API) | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 03/03/2017 | |
| ms.prod | sql | |
| ms.prod_service | database-engine | |
| ms.reviewer | ||
| ms.technology | stored-procedures | |
| ms.topic | reference | |
| apiname |
|
|
| apilocation |
|
|
| apitype | DLLExport | |
| dev_langs |
|
|
| helpviewer_keywords |
|
|
| ms.assetid | 805e68e1-d17f-41bd-8b9f-a27283bb6fbe | |
| author | rothja | |
| ms.author | jroth |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
Important
[!INCLUDEssNoteDepFutureDontUse] Use CLR integration instead.
Checks whether the current connection or task needs to be aborted and returns TRUE if the connection is killed or the batch is aborted
BOOL srv_got_attention (SRV_PROC *
srvproc
);
srvproc
Pointer identifying a database connection.
TRUE if the connection is killed or the batch is aborted. FALSE if the connection or batch is active.
A long-running extended stored procedure should check the server attention by calling srv_got_attention periodically so that the procedure may terminate itself when the connection is killed or the batch is aborted.
Important
You should thoroughly review the source code of extended stored procedures, and you should test the compiled DLLs before you install them on a production server. For information about security review and testing, see this Microsoft Web site.