Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
 Posted - 2006-01-04 : 04:39:42
|
| I'm back...Has anyone installed sqldebugger and what's it for?Honestly speaking, I haven't seen this account in most of the systems I've installed.TIA--------------------keeping it simple... |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2006-01-04 : 06:48:25
|
| Hi Jen, welcome back.I'm guessing you're referring to the built-in SQL debugger described in Ken Henderson's books?I tried it a few times. I find inserting selected PRINT or SELECT statements in stored procedures is more useful than using the debugger. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-01-04 : 07:42:31
|
I can't get along with having to type all the parameters to the SProc - particularly the datetime ones (IIRC) with the rigid, verbose, format that they require. So I'm right behind Sam with my PRINT and SELECT statements!For what its worth our sprocs have:CREATE PROCEDURE MySProc @MyParam1 varchar(10), ... @MyParamN varchar(10), @intDebug int=0 -- 1=Debugging is ONAS... IF @intDebug >= 1 SELECT [MySProc] = 'DEBUG(1)', [@FOO]=@FOO, ... ... EXEC MyOtherSproc @MyParam1=@MyParam1, ..., @MyParamN=@MyParamN, @intDebug=@intDebug so that when an SProc goes hooky I can just re-run it in Query Analyser with an extra ", @intDebug=1" on the end and see what DEBUG stuff I get out. Note that @intDebug cascades to child-sprocs.I've not idea what overhead leaving the "IF @intDebug >= 1 ..." stuff in Production code adds to runtime ... anyone know?Kristen |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-01-04 : 19:43:42
|
Hi Sam,Kristen, it's nice to be back online. I was actually missing you guys  I don't know if I'll agree because I haven't used the debugger yet.So, if I remove the sqldebugger account, debugging will not be possible? How does it work? It's a local account and are there services using it?If the developers still want to use the debugger, what's the minimum permission that I can allow?TIA--------------------keeping it simple... |
|
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2006-01-04 : 19:57:45
|
Lots of questions, so little time...  Google sqldebugger and you'll see a few posts from people having problems with the username. As to permissions, that shouldn't be a problem because you shouldn't allow sqldebugger to be run on a production database. I've read it locks all resources in the database. It's a test-system only utility, where (in my case) permissions come cheap! |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-01-04 : 21:32:46
|
| Thanks Sam, I actually did a google before but the questions remained unanswered (probably because of the effort it takes to set it up and troubleshooting issues )Yeah, I agree debugging should be left at the dev stage--------------------keeping it simple... |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-01-05 : 05:07:08
|
| "probably because of the effort it takes to set it up and troubleshooting issues"I haven't done it in a while, so can't tell you the answer off the top of my head, but it is straightforward BUT there are some prerequisites.I'm pretty sure they've come up here, and the answers were clear, so perhaps a Google for:site:sqlteam.com sqldebuggerwill get you a better class of Goggle result!Kristen |
|
|
|
|
|
|
|
|
the bugger?