They??™re case-sensitive, and any misspelling
causes the job step to fail. For detailed information on the use of tokens, search for
???token??? in the Books Online index.
Agent Proxies
One issue with previous versions of SQL Server was limiting the security context used
when executing an unattended job. Remember that a job can take on a number of execution
forms, such as a T-SQL statement, an operating system command, or even an
ActiveX script. Most users can create a job in at least one of those forms, so there needs
to be a way to limit what they can do. With T-SQL, having the proper security on the
database is sufficient, but for an operating system command or an ActiveX script, the
number of items to secure can be daunting to manage.
Both SQL Server 7.0 and 2000 provided the ability to limit the execution of
command-shell scripts and ActiveX scripts to administrators only. It also provided a
proxy account that you could use to limit the security context if you did allow that execution.
In SQL Server 7.0, that account was a fixed account, meaning that it had a fixed
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 117
account name, but in SQL Server 2000, the administrator could select which account was
to act as the proxy.
Pages:
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246