About the Author
With security clearance and well over a decade of experience with SQL Server, Web Monkey is the resident DBA at
Norb Technologies and a real database guru.
A regular contributor to SQL Server Club, his background includes software development, hardware, a
smattering of essential networking knowledge and an unhealthy interest in web security. He has an obsession with
automating repetitive tasks, but has a tendency to forget where he left his last open bag of fruit and nut...
Welcome back... 12. Select the Default instance:
If the Default instance radio button is disabled, this probably means that there is another, default instance of SQL Server 2000 or SQL Server 2005 already installed on this machine. In this case, consult the DBA for the project as it may not be necessary or desirable to re-install the database components.\
Click on Next. |
13. Select the radio button Use the built-in System account: |
The first step will change the Windows account under which the SQL
Server service executes to the Local System account.
In a production environment or certain development environments, it
may be desirable to change this to a domain user account, but this is
not usually necessary for local developer
installations. Note that the service account settings can be changed
through the Services applet in the Control Panel at any point after
installation, however SQL Server will require
re-starting in order for these changes to take effect.
Click on Next. |
14. Change Authentication Mode to Mixed Mode and set a password for the sa logon. The user’s NT logon name could be used as an initial password, but note that whatever is used, it should NOT be the same for each machine as the sa account gives sysadmin privileges to any user who uses it: |
Click on Next. |
15. Keep the default collation settings, UNLESS the DBA for the project specifies that they should be changed. Be aware that certain applications require non-default settings: |
Click on Next. |
16. Select Error Reporting and Usage options – it does not matter what these are set to, as they are completely at your discretion: |
Click on Next. |
17. The pre-installation screen will now appear: |
Click on Install. |
18. The Setup Progress screen will appear, informing you of installation progress: |
This step usually takes 10-30 minutes, but requires no user intervention - so now's a good time to take a break and make some coffee. |
19. The Setup steps have completed: |
Click on Next. |
20. The Completing Microsoft SQL Server 2005 Setup screen will now appear: |
If you only want the database server to be accessible from the machine on which it is installed, click on Finish. SQL Server 2005 installation is now complete. However, if you wish the database server to be accessible from other machines, click on the Surface Area Configuration tool link. |
21. The Help Protect Your SQL Server screen will appear: |
Click on the Surface Area Configuration for Services and Connections link. |
22. The SQL Server 2005 Surface Area Configuration screen will appear: |
Click on the Remote Connections node in the left hand tree pane, then click on ocal and remote connections.
By default, TCP/IP only is selected and is usually sufficient in
most development environments, but if you suspect that you may need SQL
Server 2005 to host legacy applications
which require support for the named pipes SQL Server communication
protocol, click on Using TCP/IP and Named Pipes. If in doubt, consult the DBA for the project.
In addition, if you wish this installation of SQL Server to
automatically announce itself on the network to automatic database
server directory queries, click on the
SQL Server Browser Service, set the Startup type to Automatic, click on Apply, then click on the Start button. Click on OK, and then close the Help Protect Your SQL Server screen. Finally, click on the Finish button on the Completing Microsoft SQL Server 2005 Setup screen. Well done - SQL Server 2005 setup is now complete. |
http://www.sqlserverclub.com/essentialguides/how-to-install-sql-server-quick-guide-part-2.aspx
0 comments
Post a Comment