Comments on: Drop all stored procedures

By: Amr ElGarhy

Amr ElGarhy — Tue, 15 Dec 2009 23:19:28 +0000

Helped me too much, nice script, did my job in no time :)

By: Pedrero

Pedrero — Tue, 20 Oct 2009 12:54:29 +0000

Thank you man

By: Simon

Simon — Mon, 10 Aug 2009 10:48:18 +0000

Fab script – saved me a good deal of trouble. One minor amend – some of my upsized procedures have dashes in the title so I made a minor change to the exec statement within the begin…end loop to add quotes around the SP name:

exec(’drop proc ‘ + ‘”‘ + @procName + ‘”‘)

Thanks again Matt. Still useful, 5 years after it was published :-)

By: Abhilash

Abhilash — Wed, 29 Jul 2009 14:46:32 +0000

Nice Post and very useful!

By: Hassan

Hassan — Wed, 06 Jun 2007 09:06:10 +0000

Thanks a lot…

By: Raymond Lewallen

Raymond Lewallen — Thu, 16 Dec 2004 14:59:31 +0000

This is a petty comment, but here it is anyways :)

Object names in Sql Server are stored as Unicode. Specifically, object names are stored using the UDT “sysname”, which is the equivalent of NVARCHAR(128). So no need to declare any variable longer than 128 characters, because the name won’t exist at a length greather than that in sysobjects. Also, varchar() is non-unicode, whereas nvarchar (and sysname for that matter) are unicode data types. I can’t remember off the top of my head where I had a problem with this in the past, but I was doing a convert to varchar from sysname and ended up with unexpected results, so use nvarchar, or better yet sysname because it enforces the 128 character limit, just to be safe. Chances are, it won’t make a hill of beans difference though. I’m just bored and wanted to post something.