Re: Opinion on change control for DBA scripts

From: Jeremy Schneider <jeremy.schneider_at_ardentperf.com>
Date: Thu, 27 Jun 2013 11:02:09 -0500
Message-ID: <CA+fnDAbQE6OjvJnJxD_eiqa5v=9bPHnd9OGWpiODvZXcxjnNBg_at_mail.gmail.com>



Good point about sharing, another common use case. And great idea to build stuff into views instead of scripts!

On Thu, Jun 27, 2013 at 10:53 AM, Dba DBA <oracledbaquestions_at_gmail.com>wrote:

> as far as generic DBA scripts... we have a directory in the main change
> control tool here under our DB Branch we call 'useful sql' and we check our
> stuff in there and then keep notes on it so we can share the scripts. This
> is mainly so the DBAs can share stuff.
>

...

> Recently, I started taking some DBA scripts and turning them into views. I
> found this easier than running them on the boxes. I like this because I can
> use oracle comments to document them and document each field. Its very
> useful when I need to give a query or something to a developer or a tester.
> I generally like to use a naming convention that denotes that its not used
> by the application. Lately I have been spelling out 'internal' in the view
> name. The nice thing about this is I can take them with me and reuse them
> from project to project. Doing the extra comments lines don't take long and
> once its done, its reusable. Comments are particularly nice since most
> developers/testers prefer a GUI tool. In SQL Developer when you click on a
> table/view the comments come up right next to the column names. Very
> convenient for them and easier for you since you don't have to explain as
> much.
>

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jun 27 2013 - 18:02:09 CEST

Original text of this message