From: esquel@sommarskog.se   
      
   Gene Wirchenko (genew@ocis.net) writes:   
   >      I am using it to set up a database.  I think that it is intended   
   > for that.  It still is missing things that surprise me.   
      
   Not really. The database consists of source code which should be under   
   version control. Handling of files is outside the scope of T-SQL.   
      
   >      I did solve my problem by creating/dropping a temporary table to   
   > create a kludgy but working flag.  Script-level variables would be   
   > much easier.   
      
   Script? Session-level possibly. A script is only something you have on   
   file, but SQL Server sees only one batch at a time.   
      
   >      I want something that I can use in SSMS.  Anything else will be a   
   > rougher ride by just the fact of having to use more than one tool.   
      
   Why would it be a rougher ride to have your computer running two programs   
   running simultaneously. Multi-tasking is quite an old concept by now.   
      
      
      
      
   --   
   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)