Re: Need DBA advices on creating a new user, application level or DBA level?

Or you could just use NQL to monitor the app and report any new users to the DBA's pager or email to keep him happy.
Scripters and Programmers,

NQL (Network Query Language) is a dynamic and innovative tool that makes it possible to retrieve information from any network, organize it in any format and deploy it across any platform including wireless devices such as the Palm Pilot VII, digital cellphones and digital pagers.

NQL sets a new standard for developer productivity, saving time and allowing comprehensive interoperability with all programming and scripting languages.

We are currently seeing an almost 90% purchase rate after companies evaluate the software including Microsoft and Ingram Micro.

To see the latest information on NQL and download a full version for a free 30 day evaluation visit our website at www.NQLSolutions.com/downloaddirect

Please contact me at 888-816-1930 for questions concerning your companies’ specific needs and how NQL can solve them.

Thank you,

I look forward to doing business with you.

Doug Manney

tstrah wrote in message <398841e0$1_at_10.32.1.3>...
>No, the app should not do it. A person should always be directly
>responsible. Depending on the app, you are exposing the DB/company to
>unnecessary security risks, e.g. giving out a DBA password to non DBAs or
>hardcoring it into scripts/programs.
>Of course, I'm biased because I'm a DBA too.
>Regards
>Tim
>
>"Jimmy" <anonymous_at_anonymous.com> wrote in message
>news:398904FD.FA8C195E_at_anonymous.com...
>> Hello all,
>>
>> Recently, my company wants to develop an application. One of the
>> functions of the application is it can create a new user. This function
>> can only be done by a project owner, such as PROJECTA_OWNER.
>> PROJECTA_OWNER is not a DBA, he is just a project owner with some system
>> privileges (such as create user).
>>
>> However, my company's DBA strongly disagree this function. He said
>> that creating a new user should be done by DBA, not on application
>> level. This is because using a client application to create a user may
>> bypass his vision, as a result, he don't know why such a user exist
>> after the application is running (since anyone who knows the
>> PROJECTA_OWNER password can create a new user). He think that it is more
>> difficult to manage the user accounts in the future.
>>
>> Now, I have some questions:
>>
>> 1) What do u think the above scenario? Should user creation done by
>> DBA, or done on application level? ANy other disadvantages if done on
>> application level?
>>
>> 2) I know that if done on application level, PROJECTA_OWNER need to
>> alter some user parameters (e.g. default and temporary tablespace etc).
>> However, such parameters may need to be hardcoded. This is not a good
>> practice since we need to recompile the program if the tablespace name
>> is changed to another name. Is there other ways to handle such
>> situation? (I think using a PL/SQL procedure to create a new user, and
>> the application is calling this procedure. This procedure is written by
>> DBA. In this way, DBA can change this procedure without affect the
>> application. Am I right)
>>
>> Any suggestions?
>>
>> Thanks,
>> David
>>
>
>
Received on Wed Aug 02 2000 - 00:00:00 CDT