Database Reference
In-Depth Information
To do this, each additional installation needed its own name. That is why it is called a
named instance
.
Before SQL 2005, the first installation always installed without an additional identifier and was by definition
the
default instance.
only subsequent installations were given a unique name.
From 2005 on, the rules changed again, and you can now install SQL, SSAS, and SSRS with an additional
identifier even on the first installation, without requiring a default instance. on your personal computer, if
a default instance is not installed, you must qualify your SQL, SSAS, and SSRS servers with the full name;
Computer Name\named instance name
.
Another method of connecting is to use the Server Name dropdown menu. Select the < browse for
more. . . > option, and then select your local machine or a network to connect to (Figure
5-5
).
Figure 5-5.
Browsing for SQL Servers
In Figure
5-5
, you can see the local servers list on Randal's laptop. Selecting one of these creates a
connection to the server as long as that database engine is running. Additionally, you can connect to remote SQL
Servers as well, as long as it is running and remote connections to the other computer are allowed.
Configuration Manager
If you want to allow a remote connection to your server, you can enable this using the SQL Server Configuration
Manager. You can also use this tool to make sure that an instance of SQL server is running on a given computer or
to manage SQL Server, SSAS, SSIS, and SSRS start-up and service account settings.
Figure
5-6
lists SQL Server services and indicates that the named instance for (local)\SQLExpress is not
currently running, but three other SQL servers are currently running. The SQLExpress named instance is set to
start up manually, whereas the other three servers start automatically when the computer boots up. As it is now,
