Is this true for sql 2000

I've been searching all over the web for an answer. I found the paragraph
below. The article says this applies to sql 7.0. Does this apply to sql
2000 and how do I get around it?
Because of the limited access to xp_cmdshell (only members of the sysadmin
role have access to xp_cmdshell using the SQL Server service account, all
non-sysadmins use the local account SQLAgentCmdExec which has no access to
domain resources), the average end user cannot export data to a UNC path.No it works differently in SQL 2000. In 2000, you can create
a SQL Agent proxy account which will be used by SQL Server
Agent to execute jobs owned by non system administrators.
This can be a domain account. You can find more information
in the books online help topic for the extended stored
procedure that is used to retrieve or set the proxy account:
xp_sqlagent_proxy_account
-Sue
On Fri, 14 Jan 2005 12:17:04 -0800, "John"
<John@.discussions.microsoft.com> wrote:

>I've been searching all over the web for an answer. I found the paragraph
>below. The article says this applies to sql 7.0. Does this apply to sql
>2000 and how do I get around it?
>Because of the limited access to xp_cmdshell (only members of the sysadmin
>role have access to xp_cmdshell using the SQL Server service account, all
>non-sysadmins use the local account SQLAgentCmdExec which has no access to
>domain resources), the average end user cannot export data to a UNC path.