Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Dropping a database Expand / Collapse
Author
Message
Posted Thursday, July 05, 2001 12:00 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, October 02, 2013 9:26 AM
Points: 265, Visits: 185
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/rsharma/droppingadatabase.asp
Post #514
Posted Monday, August 13, 2001 1:32 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, May 01, 2013 6:34 AM
Points: 11, Visits: 2
Hi Rahul,
I will find the script very useful,tho i have one question,
what are u executing when u said :
EXEC SetMessages

Thanks.




Post #19797
Posted Monday, August 13, 2001 11:03 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, October 02, 2013 9:26 AM
Points: 265, Visits: 185
Patti:

The script has an error....I was using SetMessages as my stored proc for having my custom error messages. You can remove that piece of code from the first proc usp_DropDB and you will be fine or alternatively you can make a change to the usp_ForceDropDb stored procedure and replace the statement in the end:
"EXEC usp_DropDB @DatabaseName"
with
SET @DatabaseName = QUOTENAME(@DatabaseName)
EXEC ('DROP DATABASE ' + @DatabaseName )

Hth,

Rahul




Rahul Sharma
Senior Database Administrator
Manhattan Associates
Atlanta, GA
Post #19798
Posted Friday, April 12, 2002 6:49 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 02, 2007 10:42 PM
Points: 1, Visits: 1
Hi, thanks for this one!

Mnd goal is to publish a content database from staging to live, safely, from an admin web page. The wrinkle is that the DB must remain alive on the web during the process ... I plan to modify the DSNs on the fly.

One small point, when I use this in SQL 7 it returns an error "You can't kill your own process."

This error was causing the calling DTS package to fail on this step.

I simply added a clause to the SELECT of spids to exclude "@@SPID" which is the current process.

SELECT spid
FROM master.dbo.sysprocesses
WHERE dbid =
(SELECT dbid FROM master.dbo.sysdatabases
WHERE name = @DatabaseName)
AND spid <> @@SPID
^^^^^^^^^^^^^

It worked fine and once again I appreciate the resource, I don't know much T-SQL ... I'm actually a web guy using Cold Fusion with SQL Server.

- Jon





Post #19799
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse