Let’s take a few minutes and go over in detail a few installation and
configuration issues before SQL is installed. The topics covered in this section can help you solve many of the problems associated with installing Microsoft SQL Server without any training or guidance. I have seen many newsgroup messages that could have been avoided had the reader followed these suggestions.
Creating Your SQLExec Account
Before you install the server software, you should take a moment to create a user account for the SQL Executive account to use once you have installed the server. This account is created with the User Manager for Domains. The name you choose is not as important as the permissions you give.
I usually choose a name that makes sense to me. “SQLExec” is used in Microsoft’s training and course materials, so we’ll use that name here. This domain account should be granted the Log On As A Service right so that it can get to the server when it needs to. Do not place any account restrictions on this login. Select a password in accordance with good security practices and make sure that the checkboxes for User Must Change Password and Account Never Expires are set properly. See Figure 2.1 on page 45 (in the Practical Guide section of this chapter) for the proper settings.
Figure 2.1 User Properties dialog box showing the SQL Executive account settings.
One More Account To Go
While I am on the subject of creating user accounts, I usually create a user account for the SQL Server service to use. It’s not a requirement for the server to use an account other than the local system, but there are some compelling reasons to do so. Having the server run under the permissions of an account
http://www.itknowledge.com/reference/standard/1576101495/ch02/039-041.html (2 of 3) [1/27/2000 6:15:27 PM]
with a password is much more secure. In the event that some unauthorized user gets access to your server, this extra security precaution can save you some headaches. When you create an account for the server, make sure you grant the same permissions as you did for the Executive service account.
This account can also be used for a mail client application. However, you should create the account before attempting to configure the SQL Mail Client or your server. In practically all mail systems, SQL Server must run under the same account as the mail client you install and configure.
Changing the account that SQL server runs under is done through the Control Panel under Services. Select the Services icon and when the window opens up, double-click the MSSQLServer service. In the Services dialog box, click the Startup button. In the bottom of the User Properties dialog box, fill in the domain name, the account name, and the password, then select OK. See Figure 2.2 on page 46 in the Practical Guide for the User Properties dialog box.
Figure 2.2 User Properties dialog box showing the SQL Server account settings.
Previous Table of Contents Next
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc.
All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited.
http://www.itknowledge.com/reference/standard/1576101495/ch02/039-041.html (3 of 3) [1/27/2000 6:15:27 PM]
Brief Full Advanced Search
Search Tips
To access the contents, click the chapter and section titles.
Microsoft SQL Server Black Book
(Publisher: The Coriolis Group) Author(s): Patrick Dalton ISBN: 1576101495 Publication Date: 07/01/97
Search this book:
Previous Table of Contents Next
Setting Up A Mail Client
If you are going to take advantage of the SQL Mail Client and email
notifications on your SQL server, you should take the time to install and test the mail client for the mail system you are running before you install Microsoft SQL Server. Using email in your applications can provide you with a proactive management tool that many systems lack.
Using the xp_sendmail external stored procedure in your triggers and user-defined stored procedures can be done very efficiently. Be aware that each mail system is configured slightly differently; you should consult the section on installing the specific mail client in SQL Books Online for any issues associated with your mail system. Microsoft SQL Server will send and receive mail from any MAPI-compliant mail system running on your network.
Some additional overhead is involved with sending mail from inside your SQL code, so expect a slight delay in the execution of scripts or triggers that send mail. Since the use of email in your code has little to do with installation, I address this topic later in the book. Mail does, however, play a huge part in setting up a proactive server that will alert you to potential problems before they get out of hand.
Make sure that you create the accounts that mail must run under, and be sure to log in as those accounts when installing the mail client software. With
Microsoft Exchange, for example, you need to set up a profile that matches the account that Microsoft SQL Server runs under as a service. Failing to do this will cause configuration problems when attempting to get mail features to work properly. I will walk through setting up a Microsoft Exchange client later in this chapter.
http://www.itknowledge.com/reference/standard/1576101495/ch02/041-046.html (1 of 3) [1/27/2000 6:15:28 PM]
Go!
Keyword
---Go!
One Last Time
I know that budgets and office politics come into play when deciding what kind of server to buy or what upgrades are required to meet your needs. Take what I have said here with a grain of salt. Few scenarios allow the
best-possible design to be implemented. Fight only the battles you feel need to be fought.
Fortunately, Microsoft SQL Server is a very robust application. You can put an awful lot on a SQL server and make it do just about anything you can imagine.
It runs well on every machine I have ever installed it on—from a 486/66 with 32MB of RAM to a huge multiple-processor beast. I have not found a bad system yet—only ones that are improperly configured.
Regardless of the server you choose to install Microsoft SQL Server on, you will be tempted to add a service or two to this server. Placing additional services on any of these servers will cause changes in the way you should configure Microsoft SQL Server. Most administrators will be tempted to place some extra files or network tasks on the higher-end machines I have talked about here. Fight that urge!
Summary
• Take time to analyze your server requirements—both current and future needs. Do not forget to consider distributed processing in your plans.
• Check out the Man-O-War Task Server on the CD-ROM
accompanying this book. This application can be a valuable tool on your network.
• Place as much RAM in your server as budget allows. The more the better, up to the 128MB range. Insufficient memory limits the number of users and lengthens query response times.
• Install your operating system and verify network connectivity before installing Microsoft SQL Server.
• Create an account for the SQL Executive and the Microsoft SQL Server service to run under. Creating these accounts will allow you to implement better security on your servers and to easily configure email services. These accounts should be granted the Log On As A Service right with a good password assigned for security purposes.
• Install, configure, and test your mail client software prior to installing Microsoft SQL Server. It is very important to ensure that mail can be sent through your client software before assuming that the SQL mail client can send mail. If you cannot send mail from the client, Microsoft SQL Server will not be able to send mail.