Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What are the things I have to consider when I have to install SQL Server (2005/2008) on a new server?

  • Storage setup
  • TempDB
  • Security

What are some common mistakes made in that process?


locked by HopelessN00b Dec 5 '14 at 3:29

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

up vote 11 down vote accepted

Please see Brent Ozar's great post on the topic:

WOW, dude, that's the first time I've ever seen somebody else quote my setup checklist. I'm flattered. I'm so used to going into these questions and copy/pasting my own link to my checklist - now somebody else is doing it for me. Love it! So of course I gotta upvote ya, heh. – Brent Ozar Apr 30 '09 at 12:07
Brent's list is very thorough, I would add: make sure anti-virus is configured to bypass sql database files either by location or extension. – SqlACID May 1 '09 at 12:08
SqlACID - great point, and I'll add that to the checklist. – Brent Ozar May 30 '09 at 23:41

I usually revoke the VIEW ANY DATABASE permission. By doing this each user can only see the databases they are able to access (it also helps simplifying the list in SQL Server Management Studio):

USE master

Not offense to Brent Ozar, but Chad Boyd also has a very good series of SQL checklists:

The cluster checklists, in particular, are invaluable.

Links have been moved for this old answer, here you can find these – icnivad Aug 7 '13 at 4:12

If you want to install the Express version, here are some tips for the network connectivity configuration:

SQL Server 2008 Express Installation Checklist

"Out of the box, SQL Server Express's network connectivity settings aren't enabled."

Talk about an understatement!


Not the answer you're looking for? Browse other questions tagged or ask your own question.