It's great
A reader, August 18, 2006 - 1:35 pm UTC
Thanks Tom, that was great. I'm sorry to bother you, I couldn't find it before the post.
One last thing, can I tweak that code to track edits too .. I've just edited a procedure with raptor and it doesn't log it in to the table.
Thank you.
August 18, 2006 - 4:25 pm UTC
they should just be doing a create or replace, I hope they are not doing a drop+create....
Can you do me a favor and see if they are doing a drop? make the trigger before create or drop...
Ahemm, EDIT??
A reader, August 18, 2006 - 4:18 pm UTC
Edit??
Please define Edit. There is no way you can edit procedures/packages/triggers. And if you edit them and then apply the changes it does a Create or Replace...
And if you cancel the changes then how will it track that??
What for SYSDBA?
Robert, August 19, 2006 - 12:03 pm UTC
Tom,
Who then should have the SYSDBA role?
Thanks,
Robert.
August 19, 2006 - 1:54 pm UTC
almost no one.
Describe what you use SYSDBA for. for most people the answer is:
I use it to startup, I use it to shutdown.
(well, they might silently add - I use it because I have it and with it, I never need to worry about being "denied access" to anything).
If that DBA needs to
a) do DBA stuff
b) startup
c) shutdown
give them DBA and sysoper
If that DBA needs to
a) do DBA stuff
give them DBA
If that DBA needs to
a) do a limited set of maintenance operations
then by all means, do not be afraid to create your own DBA roles "DBA1, DBA2, ..." and use them instead.
You hit the nail on the head!
Robert, August 19, 2006 - 1:59 pm UTC
Tom,
You hit the nail on the head! :)
<quote>
(well, they might silently add - I use it because I have it and with it, I never need to worry about being "denied access" to anything).
<quote>
Thanks,
Robert.