My friend and former co-worker Chris Rock just posted at article over at SQLTeam.com that has a pretty good walk through of how to set up and use the VS debugger on procs. According to an MSDN article he includes it still requires sysadmin permissions to debug though, limiting it to local dev instances or a dev server at best. Why can't we have the equivalent of the alter trace added in SQL 2005 for debugging? I often complain that developers treat TSQL as if it's magic incantations instead of another kind of code, and having to debug using print statements isn't helping the situation.
I'm Andy Warren, currently a SQL Server trainer with End to End Training. Over the past few years I've been a developer, DBA, and IT Director. I was one of the original founders of SQLServerCentral.com and helped grow that community from zero to about 300k members before deciding to move on to other ventures.