From: esquel@sommarskog.se   
      
    (rja.carnegie@gmail.com) writes:   
   > Well, my grand scheme includes (1) writing a stored procedure   
   > that defines, say, ten or twenty indexes and statistics on a   
   > table, but allows them to be created one by one, and,   
   > (2) using the same interface to perform "index rebuild"   
   > and "update statistics" on the target - that part isn't   
   > done yet.  And this is where the table may be called   
   > Student_2011, Student_2012, Student_2013, and may be in   
   > database UserStuff01, UserStuff02, UserStuff03, and so on:   
   > the interface stored procedure addresses that complexity.   
   >   
   > I also want to avoid having the server do some of this meta-work   
   > more than once.  Except that it deletes a lot of the data every   
   > day and loads it in from where it came from again.  So, make that   
   > "more than necessary".   
      
   Not sure where you are heading here. Even if you add statistics manually,   
   SQL Server will still maintain them, just like it maintains autostats.   
   Or do you plan to turn off automatic updates of statistics for the   
   database?   
      
   --   
   Erland Sommarskog, Stockholm, esquel@sommarskog.se   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)