|
|
|
|
|
SQL Server Agent 1 2 3 4 5 6 7 8 9 If you have the capability to send pager e-mails, you can setup the appearance of those messages on this tab. You should always specify a fail safe operator. This operator should be configured for every notification mechanism: e-mail, page, and net send that is available to you. This operator is notified if the notification system could not contact the operator specified within its job step or alert. This is your insurance policy that any notification will always get through to at least one operator.
Job system properties. Each job that is executed will create an entry in a history log. You will want to limit the size of the job history log and also the number of entries maintained for each job in order to avoid overflowing the msdb database. CmdExec and ActiveScripting job steps can directly access the machine and other resources with the full authority of the NT account the SQL Server Agent is running under. You will normally want to restrict access to these types of job steps to only those with a SysAdmin authority.
Connection properties. Because this was done on a Windows 98 machine, the Windows NT login option is not available. If at all possible, you should configure the connection to use Windows NT authentication because NT has more robust security features than SQL Server.
|
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.
