I need to have a client process create dump devices; however, I've discoverd
that only the SA can use sp_addumpdevice. Any suggestions for a work-around?
Tony Burnett
by Tony Burne » Tue, 24 Feb 1998 04:00:00
I need to have a client process create dump devices; however, I've discoverd
that only the SA can use sp_addumpdevice. Any suggestions for a work-around?
Tony Burnett
by Neil Pik » Tue, 24 Feb 1998 04:00:00
Tony,
You could copy the text to another stored-procedure and remove the
code that checks for sa. Or you could just remove the check.
Obviously there are upgrade/compatibility issues with doing either of
these.
Neil Pike MVP/MCSE
Protech Computing Ltd
by Sergei Didu » Tue, 24 Feb 1998 04:00:00
There is internal logic in sp_addumpdevice SP, that allows only SA run it.
(you must be System Administrator (SA) to execute this stored procedure).
Try to write your own version.
--
Sergei Didur
Systems Analyst
Quote:> I need to have a client process create dump devices; however, I've
discoverd
> that only the SA can use sp_addumpdevice. Any suggestions for a
work-around?
> Tony Burnett
by Tony Burne » Wed, 25 Feb 1998 04:00:00
Tony Burnett
1. Non SA Account cannot start Scheduled Job
[1] Do a 2-phase authentication. when the user passes first authentication
then reconnect him/her
as a SA.
[2] In SQL, assign SA as an alias to that user.
2. exchnage server - global address list for external contacts ?
3. Proxy SQL Server Agent Account for Non SA Users
4. Stored Procedure & Access 2000
5. running sp_detach_db from a non sa account
6. OFERTA DE TRABAJO (FREELANCE)
7. Help!! - issue sp_addlogin from a non-SA account
9. non sa owner viewing sa owned jobs
10. SA privilegia to non-sa user
11. Announce: granting SA-commands to non-SA users
12. Installing SQL2000 SP1 kills sa and builtin\administrator accounts