November 15, 2002 at 11:35 am
A single installation of SQl2000 SP2 contains the following
User A owns database 1.
User B owns database 2.
User A can read user B's database and vice versa.
Neither are admins.
User A wrote a stored procedure to extract data from user B's database and store the data in a table in his database.
He is using DTS to schedule the procedure. Don't ask why. I know the SQL Agent can handle this, but I'm just the DBA.
Since User A is not an Admin, I have to set up the Proxy Account to permit him to schedule his procedure.
Question:
If I setup the Proxy account, with read and write permission on User A's database and Read Permissions on User B's, would that be all that is required? Any advice on this would be much appreciated.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
November 18, 2002 at 8:00 am
This was removed by the editor as SPAM
November 18, 2002 at 11:13 am
I did some digging in Tech Net and I have a partial answer. The Q269074 article explains it quite throughly. However, the article only addresses the win2k environment.
Here is a quote:
"For the jobs that execute a DTS package, the SQL Agent Proxy account must have read and write permissions to the temp directory of the Account the SQl Server Agent is running under."
The above quote does not apply because we are using an NT 4.0 server.
I'd like to setup a proxy account that can read both databases and write to the database the data is stored in. I'm going to give the proxy account access to c:\temp and winnt\temp and see if that is all it needs. If anyone has done something similar and has any feedback, it would be appreciated.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply