Home Dashboard Directory Help
Search

Selecting the "Default Instance" option in SQL Server 2008 Express RTM has no effect by StephenA


Status: 

Closed
 as Fixed Help for as Fixed


9
0
Sign in
to vote
Type: Bug
ID: 361809
Opened: 8/14/2008 3:22:05 AM
Access Restriction: Public
3
Workaround(s)
view
5
User(s) can reproduce this bug

Description

When installing SQL Server 2008 Express RTM, selecting the default instance option still results in the database engine being installed as the instance named SQLEXPRESS.

As a workaround you can select the option to install a named instance and enter "MSSQLSERVER" as the instance name.
Details
Sign in to post a comment.
Posted by Stephen Braddy on 11/29/2009 at 7:45 AM
Bug still exists. I recently downloaded the "SQLEXPRADV_x64_ENU.exe" from the following page (which is linked from the main SQL Server 2008 Express download page):

http://blogs.msdn.com/sqlexpress/archive/2009/06/15/installing-sql-server-2008-guidance.aspx

This bug still seems to exist. I re-installed twice before figuring out what was going on. Is this supposed to be fixed yet?
Posted by InteXX on 4/28/2009 at 4:42 PM
The bug still appears to exist, as the download file hasn't been updated since 8/22 of last year:

http://www.microsoft.com/downloads/details.aspx?FamilyId=B5D1B8C3-FDA5-4508-B0D0-1311D670E336

This is the landing page linked to from the main SQL Express download page, so if there's an update the link should be changed. Otherwise it seems a long time to fix such a simple issue.
Posted by Microsoft on 1/22/2009 at 10:25 AM
Until PCU1 becomes available, you can try the following workaround:

Select "Named Instance" radio button on the page, and manually enter "MSSQLSERVER" to install a default instance for Express instance.

Thanks,

Max Verun
SQL Server
Posted by simbolo on 1/13/2009 at 2:40 PM
Freshly downloaded on13th January 2009 from microsoft.com, I downloaded SQL Expresss 2008 with Advanced Services. Bug still exists.

A public update is a bit useless when the program isn't installed yet, please update your installers.

I had to remove/install a few times before I could figure out what was happening. It was easier to do that, than update all my connection strings in various applications all over the place.
Posted by Microsoft on 1/6/2009 at 12:41 PM
Just an update on the issue you reported. This is fixed in PCU1 which will become public soon.

Thanks,

Max Verun
SQL Server
Posted by a2af on 11/17/2008 at 6:16 AM
Now I install Sql Server 2008 Express w/Advanced Services - the same problem with default instance. Bug still exists.
Posted by Microsoft on 10/2/2008 at 9:59 AM
Thanks for reporting this issue. We have another work item that had been filed already on this. I am closing this as a duplicate, but be assured that we will provide a fix for this in the first public update (PCU).

Thanks,

Max Verun
SQL Server
Posted by smills34 on 8/27/2008 at 1:06 PM
Bug is also present in the Sql Server 2008 Express w/Advanced Services installer (downloaded 8/27/2008). Hard to believe something like this was missed.
Posted by Mikhail Kalatchev on 8/24/2008 at 5:25 AM
Very annoying bug. I had to reinstall SQL 2008 Express twice, before i look at the "Ready to install" page of wizard carefully and realize that something in install is buggy. It seems SQL team was under great presure for rlease date, to miss something very important in installation. Anyway, described workaround works, at least for me. Be carefull when insatlling SQL Server 2008 Express on production computers.
Posted by Microsoft on 8/15/2008 at 2:58 PM
StephenA1,

Thanks for the report! We'll investigate and let you know what we find.

-Richard Waymire
Sign in to post a workaround.
Posted by PeterKSL on 12/5/2009 at 1:32 AM
Steps:
1. install the "SQLEXPRESS" instance the 1st time
2. reopen the "SQL Server Installation Centre" again (under "Configuration Tools")
3. install the "Default Instanace" this time
Posted by Shtin on 2/18/2009 at 5:22 AM
MSSQLSERVER works!!11
Posted by StephenA on 8/14/2008 at 3:24 AM
Select the named instance option and enter "MSSQLSERVER" as the instance name.