XPost: microsoft.public.sqlserver, microsoft.public.sqlserver.misc,   
   microsoft.public.sqlserver.programming   
   From: reb01501@NOyahooSPAM.com   
      
   Mojo wrote:   
   > Hi All   
   >   
   > Apols if this a noddy question, but I just can't fathom it!!! :0)   
   >   
   > I use a long SQL script (DDL ??) to drop, create and populate my db   
   > each time (rather than a backup) and initially the DB needs key   
   > values inserted into it.   
   >   
   > At the mo, I try to remember to scroll up and down the script (quite   
   > long now) to populate it with the required values for the given time,   
   > but I much rather do what I used to do in MySQL, which was to put   
   > varaibles at the very top of my script so that the values entered at   
   > the top then reflect further down, eg   
   >   
   > Line 1 :    SET @MyYear= 2012;   
   > ...   
   > ...   
   > ...   
   > Line 304: .INSERT ... .... ....., @MyYear, ... ....   
   >   
   > I've tried this, but it appears as though my GO statements stop it   
   > from working.  I'm probably wrong, but this seems to suggest that I   
   > need to set the var about 1 or 2 rows above the actual INSERT, which   
   > defeats my purpose.   
   >   
   > Is there a way round this?   
   >   
   The only way is via CONTEXT_INFO(). See   
   http://weblogs.sqlteam.com/robv/archive/2012/06/05/t-sql-tuesday   
   31-logging-tricks-with-context_info.aspx   
      
   But be aware of its limitations, especially being limited to   
   varbinary(128) - in your case, that doesn't seem to be an obstacle.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)