From: genew@ocis.net   
      
   On Thu, 31 May 2012 22:26:13 +0200, Erland Sommarskog   
    wrote:   
      
   >Gene Wirchenko (genew@ocis.net) writes:   
   >>      I have not read anything stating about a CREATE PROCEDURE having   
   >> to be the only command in a batch.  But, as my post shows, I have   
   >> discovered it myself.  Curse incomplete docs.   
   >   
   >The third paragraph in the Remarks section for the topic for CREATE   
   >PROCEDURE in Books Online reads:   
   >   
   >   The CREATE PROCEDURE statement cannot be combined with other Transact-SQL   
   >   statements in a single batch.   
      
        I have not been able to find BOL on Google.  Is there a link?  I   
   have been using MSDN.  I see now that I missed that bit, but that was   
   a different page than what I had been reading prviously.   
      
   >>>Again, put your source code under version-control and load the files from   
   >>>a client-side program. Then you don't need to ask these questions.   
   >>   
   >>      I am experimenting in SSMS.  I do not want the overhead.   
                ^^^^^^^^^^^^^   
   >So you have all your procedure in a single monolithic script. A week   
   >after deployment a bug discovered. Then another bug. And so on. Do   
          ^^^^^^^^^^   
        The two words that I have highlighted do not mean the same.   
      
   >you edit the big script over and over again? And since it creates tables   
      
        Yes, I am experimenting.   
      
   >that already exists, it's pretty useless by then.   
      
        Since it starts by dropping the database, no.   
      
   >But if you want to redo mistakes others have already have made, please   
   >go ahead.   
      
        Overornamentation is a mistake others have made.  I am avoiding   
   it.   
      
   Sincerely,   
      
   Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)