You might want to add something else to exclude statisics...

Do not shrink databases. Period.  Fragmentation both at the database level and the file level is the result.  There are execeptions, of course, but in general, do NOT shrink databases.

Heh... no way... two in the same lifetime is well enough for me   Learned a lot, laughed a lot, and puked a lot......

What "language" is the "For Each loop container" written in?  Seems like anything that can use wild cards should do...

No... all you need is to point BCP at the data on the other machine using a UNC... of course, BCP should be able to "see" it with the appropriate...

Thanks for the feedback, one and all... funny how the telcom business seems to need it the most

Or, without variables...

 SELECT d.Number1,
        d.Number2,
        (d.Number1 + d.Number2) AS Number3
   FROM (--==== Derived table "d" does the aggragates once
             -- so outer select can reuse them with ease
         SELECT (SELECT...

Heh... TempDb.mdf of 100Mb???  We start ours at 12 gig on boot up with growth settings of 500Mb.  And, yes, we've found a huge performance benefit in having it that large...

I went to the doctor once and said "Doc, if I hold my arm up like this, it hurts like hell."  The doctor said "So... don't hold you arm up...

Close... very close... but, that way will prevent an Index Seek if have a usable index on the column(s) because you're doing a calculation (subtraction) on the column.  Best you'll ever...

First, very high congratulations on establishing full control of the production system.

So far as using an unattended system to install the procs in the production system goes... I wouldn't do...

All good ideas... Thanks, Carl!

Shhhhh!  My ol' friend Serqiy will hear you!  

Thanks Carl,

Yeap... the thing about the proxy needing to be available is pretty much what books online said... thanks.

Heh... Maintenance plan?  What's that?   Doesn't everyone know that a database is just a place to hold data for the GUI?