Manually installing SQL Server 2008 R2 Express or 2012 Express (instead of running WaspManualInstall.bat or WaspAutoInstallSQL2012Exp.bat):
Make sure that the PC name isn't the same as the logged-in Windows user. If they're the same, SQL won't install right. If the user can't/won't change one of them, see the article linked below "SQL 2008 R2 or SQL 2012 Express fails to install - Windows user is same as PC name".
During the installation, use these settings where appropriate:
Install the management tools, including SQL Server Management Studio Express. These options should be checked by default.
If you want to change the installation path (e.g. you want to change which drive the program and data files are installed to):
Feature Selection screen: These are less important in terms of consuming drive space. Make changes to:
Shared feature directory
Shared feature directory (x86)
Instance Configuration screen: This is the path to the instance's SQL Server executable and data files, so it is the important one. Make a change to:
Instance root directory
Named instance: WASPDBEXPRESS
This should automatically update the Instance ID, which should also be WASPDBEXPRESS
Note: Standard and Professional editions must use this instance name. The Enterprise edition can use a different name if desired but for ease of updates and support, we recommend using this instance name.
Server Configuration screen:
Service Accounts tab: On a domain controller, the Database Engine username is left blank, and the installer will not proceed, complaining that it can't use Network Service. Tell the user that Microsoft recommends against this configuration, but if they want to proceed, we have a workaround. If they agree, specify NT AUTHORITY\SYSTEM with no password (we will change it later).
- Set the SQL Browser startup type to Automatic.
- SQL 2012: Change the Account Name for the SQL Server Database Engine to NT AUTHORITY\SYSTEM, with no password.
Collation tab: Make sure it's "SQL_Latin1_General_CP1_CI_AS". If not, click Customize, then the 2nd radio button, and select the correct one. The PC's system locale determines what is chosen automatically, so it might not get set correctly for non-US users, and they'll get database errors in the client.
Database Engine Configuration screen:
Mixed-Mode (Windows and SQL Authentication)
After the SQL installation completes, open Services and restart it. If there's no error, this usually means it installed successfully. Next:
1. enable TCP/IP in SQL Server Configuration Manager.
2. If you had to specify NT AUTHORITY\SYSTEM, change that: In the Services list in Windows, edit the Log On tab of the SQL Server (WASPDBEXPRESS) service to specify This account: Network Service (with no password) which is the usual account used.
3. Restart the SQL Server service so these changes take effect.
If you don't do the SQL Browser part and/or the TCP/IP part, clients on other PCs will get SQL Error 26.