Whenever I install a standalone SQL instance (installing on a failover cluster adds a few more steps) on a x64 host (who would install SQL on a x86 in 2012?), I always do the following:
I install the latest version of Red Gate SQLBackup.
I affect Microsoft prescribed best practices for TEMPDB optimal concurrency. As part of this I add the 1118 trace flag to the startup parameters of the SQL service.
I implement the AWESOME indexMaint process published by @SQLFool
I install Ola's SQL maintenance process.
I install the latest version of SQLPSX and ponder the awesomeness of Chad Miller.
I set my Powershell profile the way I like it and import the SQLPSX modules in my profile.
I install Adam Machanic's peerless sp_WhoIsActive.
I install sp_Blitz from the good folks at Brent Ozar PLF.
I add the instance to my Ignite monitoring.
I add the host and instance to my implementation of Muthasamy Kumar and Yan Pan's wonderful SQL_Inventory PoSH process.
How about you? What steps do you like to take when you install SQL on a new machine?
Interesting to use both
Interesting to use both Michelle's script and Ola's - do you have the Hallengren IndexDefrag job to use Michelle's proc instead?
Ola's backup scripts alone make it a must
I really love Ola's solution for the backup jobs. I do a LOT of SQL installs, plus attend meetings, have project work, etc., etc - so the ability to jump on a new machine and bang out a robust backup solution that integrates with Red Gate SQLBackup is simply phenomenal.
Michelle's idexDefrag process is awesome. I run it a few hours before each work day.
I run Ola's indexDefrag process once a week (as I do the DBCC jobs that also come with Ola's solution) and that's possibly unnecessary, but what the heck...