XPost: microsoft.public.sqlserver.programming   
   From: hvandenberg@xs4all.nl   
      
   With GO's intertwined in your .SQL file, I would recommend you debug the   
   .SQL by selecting the batches one at a time and execute the selection.   
   That works for me.   
      
   On 05-04-2011 05:04, Gene Wirchenko wrote:   
   > Dear SQLers:   
   >   
   >       Occasionally, I make an error and SSMS reports this.   
   >   
   >       Actually, I make a lot of them.  There is a frustration that the   
   > line number given by SSMS is rarely the line in my .SQL file since I   
   > have a lot of GOs in it.  I am putting together a simple database a   
   > bit at a time, and I find it easier to drop it and restart on each   
   > change so as to simplify debugging.   
   >   
   >       How do I find out the actual line number?  If I am fortunate   
   > enough to recognise the GO section where the error is, I can position   
   > to the beginning and add the error line number given minus one to get   
   > the actual line number.  This is tedious.  If I can not tell which GO   
   > section met with disapproval, it is even worse.  This is even more   
   > tedious.   
   >   
   >       Please tell me that I am overlooking a setting.  And what it is,   
   > course.  I will probably post the .SQL once I have finished.  There   
   > should be a few procedures in it worth snagging.   
   >   
   > Sincerely,   
   >   
   > Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)