Post reply

Cannot Open Debugging in Query Analyser

  • January 5, 2006 at 5:47 am

    #92893

    Posted - 12/26/2005 :  07:46:23  Show Profile  Email Poster  Edit Topic  Reply with Quote

    Help needed urgently, people! I have upsized an Access app to SQL Server (it has been running with linked tables on 12 workstations and the network is now at walking pace.) I have just started working on creating Stored procedures, User-defined functions, etc. and have an urgent need to use Query Analyser to do a line-by line debugging of my T-SQL code.

    My database is on my laptop only, at this stage, and connected to SQL Server group, (local) (Windows NT authentication). I tried to get the Query Analyser/Debug process working, so I could set break points and step through the code. However, these were greyed out and I am getting the SQL Query Analyser Message,

    "SP debugging may not work properly if you log on as 'Local System Account' while SQL Server is configured to run as a service.. You can open Event Viwer to see details. Do you wish to continue?" (Buttons for Yes, No, and Cancel).

    I consulted Robert Vieira's book, "SQL Server 2000 Programming" (pages 418-420) on 'Setting up SQL Server for Debugging", which stated I should "use an actual login account" instead of the LocalSystem account. I followed his instructions, and

    1. In Enterprise Manager, right-clicked on "(local) (Windows NT)" server, selected "Properties" and clicked on the "Security" tab.

    2. At Start and run SQL Server in the following Account, I followed advice, (using "Windows Authentication") and selected the "This Account" option and proceeded to try and enter an account and password. The end result is that this somehow failed and I could no longer open SQL Server.

    I can now get back in, but cannot get past the above dialog window.

    I am still trying to create SProcs and UDF's, but it is very difficult without being able to debug the code.

    Can somebody please advise what I should do to recover the situation.

    PS, I also tried changing from Windows Authentication to SQL Server password, without effect.

    THings are getting desperate here, so I hope you can steer me in the right direction please.

    Lester Vincent

    Sydney, Australia

  • January 5, 2006 at 9:05 am

    #612921

    Sounds like you're having a rough day.

    Here's a few things to check. First, double check the account the SQL Server is starting with and I'd make it an administrator. I know this isn't required, but the debug process is a little flaky. You can remove this later once it's working and see if that breaks it.

    Second, be sure that the account is a system administrator. SQL should take care of this, but double check.

    Next, be sure you are connecting (windows or sql auth) as an administrator.

    Now try debugging and see if that helps.

  • January 6, 2006 at 12:36 am

    #613107

    Thanks for your reply, Steve.   Still haven't been able to crack it yet.    Don't know why SQL Server makes it so difficult to get into.

    I am writing code on a single machine, unconnected to any  network domain, using "Windows Authentication".

    When I try to set up, using "This Account", and enter a password, the end result is that I get the deadly Red square, which means I am shut out of SQL Server completely.

    So far, I have not found a way of getting in, except via "Local System Account", which permits opening Query Analyser's step-by-step processing facility.

    Result is, (as I am in a very tight time frame to deliver this conversion to SQL Server application), that I have spent the last 12 hours trying to get a sproc with three UDFs workingf, without being able to see what is wrong with it.

    Have tried many ways around it.

    If you have any "simple", step-by-step method of solving this, I would be enternally grateful, Steve.

    Regards,

     

    Lester Vincent

    Sydney

    PS Hope I'm in the correct forum for this issue ...   If not, please correct me.

  • January 9, 2006 at 5:25 pm

    #613700

    I'm not sure if this will help you but I have had many problems trying to get the debugger work.  And I just decided to test my debugger again to help you with your problem and I realized we had just migrated to XP.  Well, my debugger stopped working again for SQL 2000.  Anyway, the way I fixed the problem with it not stepping through code (greying out those options) was updating to the Service Pack 3.  I also received the "event viewer" message also.  The service pack I upgraded to is available here:

    http://www.microsoft.com/downloads/details.aspx?FamilyId=90DCD52C-0488-4E46-AFBF-ACACE5369FA3&displaylang=en

    I don't know which SQL edition you are using but I use the standard edition so I installed the SQL2KSP3.exe.

    I am also including a link to microsofts site for their T-SQL debugging articles.

    http://support.microsoft.com/default.aspx?scid=kb;en-us;280101

    Sorry I didn't see your post sooner.  I hope this helps.

  • January 9, 2006 at 6:26 pm

    #613705

    Thank you, John.   Nothing has work so far for me, and I welcome your reply. 

    I will follow up on your advice and will let you know the result.

    I have some pretty involved SProcs to do and getting this debugger to work is going to save heaps of time if it works.

    Regards,

     

    Lester Vincent

    Sydney

     

      

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply