From: esquel@sommarskog.se   
      
   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.   
      
   >>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   
   you edit the big script over and over again? And since it creates tables   
   that already exists, it's pretty useless by then.   
      
   But if you want to redo mistakes others have already have made, please   
   go ahead.   
      
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)