Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

I ran the SQL Server 2008 R2 Install on my Windows 7 Professional (32bit) os. Everything ran fine, no errors. I ran the SP1 install, again, all green, no errors. I run the System Configuration Checker - all green, no problems. I do not see SQL Server under my services.

I open SQL Server Configuration Manager and there is nothing showing under SQL Server Services. I try to connect to Database Engine (local) under SQL Server Management Studio and get the prevalent "cannot connect" error dialog.

So what's that all mean, it passed all install and configuration checks and then doesn't run? Should it be in my Services console?

Also, I have VS2010 installed prior and read somewhere I cannot install SQL Server after this - correct? So the configuration checker fails to find such an obvious conflict?

share|improve this question

closed as off-topic by Iain, TomTom, Rex, mdpc, squillman Jun 19 '14 at 15:32

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is dedicated to professional system and network administrators. End user and enthusiast questions are off-topic (contact your system administrator or hire a professional to help you out). Please see the Help Center for more information." – Iain, TomTom, Rex, mdpc, squillman
If this question can be reworded to fit the rules in the help center, please edit the question.

Are you sure the Database Engine component was selected during the initial install? If you browse to Programs and Features (Control Panel), select SQL Server 2008R2 and click "Change", you will be able to see which components were included. – jscott Apr 23 '11 at 0:45
I think jscott may be on to something. I believe the default install options on a "client" OS are client tools only.... – Toby Meyer Apr 23 '11 at 3:50
Ahh, yes, you are both right. I missed the option thinking is was for replication and full-search. I didn't fathom that the default install of SQL Server would not actually install the database engine lol. – DaveO Apr 24 '11 at 3:31

If you had run SQL 2008 R2 Express, then by default it will create a EXPRESS instance. (In services.msc, check if a service named SQL Server (SQLEXPRESS) is present.)

If you had run SQL 2008 R2 STD/Enterprise, then by default it will create a Default instance. (In services.msc, check if a service named SQL Server (MSSQLSERVER) is present.)

Also VS2010 by default installs SQL 2008 Express (not R2).

AFAIK, there is no SP1 for SQL 2008 R2. There are just Cumulative updates available.

And finally as @ jscott mentioned, you can try running SQL 2008 R2 installation again and check if it detects any other instances that are installed.

share|improve this answer

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