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 |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2007-03-07 : 08:39:27
|
Maryam writes "HiI have a big problem.Why I couldn't debuge stored procedure in query analyzer?Should I install SQL with special settings or should it configure?Should I debuge just in server or I can do in local system too?when I use debuger firstable it accoures an error which say :"SQL debuging may not work properly if you log on as "local system account" while SQL server is configured to run as a server. " Then it execute stored procedure but return Zero.What does this message mean?Could you give me some notes about debuging?I look forward your answerMaryam" |
|
rlaubert
Yak Posting Veteran
96 Posts |
Posted - 2007-03-08 : 11:42:58
|
Went I teach writting SP we start with writting the script first and ensuring that it works. IE remove the Create Procedure x as portion of the script. If the SP accepts or returns values you will have to use the declare statements as well. Once everything works and returns the values that you expect simple redo teh declares and add back in the create procedure and test.SP should be run in the same server configuration as they are designed. If in doubt, modify the server configuration as part of the procedure. OTherwise the results may not be correct.As long as the local server and the production server have the same database design, you should be able to do it in either place. I prefer using my local copy rather than messing with a production machine. All of my developers have local copies or use a development server for all their coding and testing. Only the DBA can add code to the production servers.Im not familiar with this error, but it sounds like 'you' are logged in using the same account 'local system account' that SQL is using. Local Systems Accounts do not have access to all resources which mean that some data outside of SQL may not be available and could effect the outcome. Whereas a user/domain account could access resources/data on other machines. If you post the procedure it might helpRaymond LaubertMCDBA, MCITP:Administration, MCT |
 |
|
|
|
|