|
|
|
|
|
SQL Server Agent 1 2 3 4 5 6 7 8 9 You will want to create a specific Windows NT account for the SQL Server Agent service and use that login. This login will need to be a member of the local administrator group or a member of the domain administrator group if you are using a Master server. The one thing you must do with this NT login is to explicitly revoke access to any resource the SQL Server Agent does not need in order to minimize the security risk. You should have a mail profile setup with SQL Mail and the SQL Server Agent should use this same profile. This gives you the ability to notify an operator via e-mail. Saving all sent messages in the sent items folder gives you the opportunity to track all of the e-mail traffic being generated. Your error log should include all execution trace messages only when you are investigating specific problems.
Advanced properties. Both SQL Server and the SQL Server Agent services should be automatically restarted if they unexpectedly shut down. Event forwarding should only be used in those cases where you are using a dedicated server to handle all messages in your enterprise otherwise it can quickly overwhelm a server. The SQL Server Agent has the ability to run jobs when the CPU is idle. This can be a very powerful addition when used properly. Setting this value to low can cause the jobs to consume resources that would otherwise be used to process user requests.
Alert system properties.
|
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.
