<div>
Thank you.That's what I did.
</div>


<div>
<div class="content wysiwyg-content">
Ran ALTER DATABASE X SET SINGLE_USER WITH IMMEDIATE ROLLBACK/SP_DETACH_DB during maintenance window around the same time that a stored procedure kicked in. Now the sp_detach_db is blocked by the stored procedure and stored procedure is being rolled back (since over 1 hour) by the sp_detach_db statement.<br />
<br />
Question: killing the stored procedure doesn't want to release it - what would happen if we killed the ALTER DATABASE SET SINGEL_USER statement?<br />
Is this safe? I checked sysdatabases and still see the database there, though Enterprise Manager says it's inaccessible.<br />
<br />
Any advice on this?
</div>
</div>


Ran ALTER DATABASE X SET SINGLE_USER WITH IMMEDIATE ROLLBACK/SP_DETACH_DB during maintenance window around the same time that a stored procedure kicked in. Now the sp_detach_db is blocked by the stored procedure and stored procedure is being rolled back (since over 1 hour) by the sp_detach_db statement.

Question: killing the stored procedure doesn't want to release it - what would happen if we killed the ALTER DATABASE SET SINGEL_USER statement?
Is this safe? I checked sysdatabases and still see the database there, though Enterprise Manager says it's inaccessible.

Any advice on this?

SQL Server 2000: sp_detach_db hung by running stored procedure

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.