| Author |
Topic |
|
keithc1
Yak Posting Veteran
88 Posts |
 Posted - 2004-06-17 : 22:51:13
|
| While debugging a SP in SQL Server 2000, in Step into, step over and other buttons are not enabled. Did i have to do some setting some where? Or how to solve this problem? I have also reinstalled but problem still persists. Web search on issue is not turning up any solutionsKeithc MCSE MCSA |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-06-18 : 00:11:15
|
Wild guess: is it something to do with SQL Server service needing to run on a domain user account, rather than SYSTEM or whatever the default is.I read about this somewhere and it is definitely preventing me using SQL debug here, but I can't remember the full symptoms.You also need SP3 for the tools (i.e. client service pack, as well as server)There's also the sp_sdidebug schenanigans ...ah, found it in BOL under "Using Transact-SQL Debugger"quote:
SQL Query Analyzer comes equipped with a Transact-SQL debugger that allows you to control and monitor the execution of stored procedures. The debugger supports traditional functionality such as setting breakpoints, defining watch expressions, and single stepping through procedures. This functionality is available when the SQL Server service uses a domain user account.In a client/server environment, the client workstation running the debugger must be a member of the same domain as the computer running the corresponding instance of SQL Server.
Maybe they left out the word "only" :)Kristen |
 |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-18 : 00:20:36
|
| Isn't that nice Kristen. You will need to grant the users access to sp_sdidebug. You shouldn't do this on production ever. You sleep the same hours as me I think.........never!!!!!!!!!!!! :)MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-06-18 : 00:56:57
|
| I never debug on production. Never ever. And my pigs are all fed and ready to fly!I got to the office at 3AM, is that unusual? ;-)Kristen |
|
|
|
keithc1
Yak Posting Veteran
88 Posts |
Posted - 2004-06-18 : 01:07:24
|
| Hey thanks for the Info, I had already run sp_sdidebug with no issues and the sqlservice account was running as domain account with admin privs. Something else is going on :( I uninstalled/reinstalled couple times, the debugger will run through the sp's just step into etc are all grayed out. LOL to make things even worse is that the latest attempt at reinstallation failed to include Northwind and Pubs DB's which I use for testing etc I'm pac'd with SP3 as well. I'm not on a prod server thank god lol if that were the case i'd a been fired by now heheKeithc MCSE MCSA |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-06-18 : 02:18:46
|
| Just to double check: You've got SP3 on client (i.e. for tools / DLLs)? and SQL server is running on [logging onto I suppose] the same domain as the workstation?Kristen |
|
|
|
keithc1
Yak Posting Veteran
88 Posts |
Posted - 2004-06-18 : 09:23:12
|
| Yes server logging into same domain as workstation, SP3 etc. The debugger works now but the Northwind and Pubs DB's were not created during the install for whatever reason.Keithc MCSE MCSA |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-06-18 : 13:56:46
|
quote:
Originally posted by keithc1
The debugger works now ...
Great! I'm curious to know what needed to be twiddled to get it going.Kristen |
|
|
|
keithc1
Yak Posting Veteran
88 Posts |
Posted - 2004-06-19 : 00:39:40
|
| Sorry for the late response to this, I ended up changing the service account to a diff named account then changing it back to what it was and i have no idea why but it started working at that point. I'm still like kind of uneasy about the install since the Northwind and Pubs DB's were not part of the install. Derrick I shose custom options installed to a diff partition than system then pretty much left all options intact, this is how I usually go about installing. I put client tools on the server as wellsince I login local time to time. I did all installs of everything localy as well because I know there can be issues with an RDP connection and install of sql server over Terminal services.Keithc MCSE MCSA |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2004-06-19 : 02:12:11
|
| Does SQL install create a log of actions somwhere? Maybe you deseleted the "samples" checkbox by accident, but it would be good to know that its nothing more sinister ...Kristen |
|
|
|
keithc1
Yak Posting Veteran
88 Posts |
Posted - 2004-06-21 : 10:25:54
|
| Derrikc thanks for the link I installed the samples that way, not going to redo a server over this issue. I looked high and low came up short as to reasons why this had happened with no luck. The one thing i didn't try was a manual uninstall of sql and if i find good info on that i may try to do it that way but i'm sure there will be a ton of registry modification to do going that path and those keys get me dizzy after a few :) Kristen thanks for your help as wellKeithc MCSE MCSA |
|
|
|
|
SQL Debugger Issues