Getting Your DBA Teams Scripts into Git

Re:Getting Your DBA Teams Scripts into Git by hobs on Wednesday July 03, 2024 @08:12AM (#40865183)

Generally the word DBA has a pretty broad meaning - and one of them is that you were a click admin that got hoisted into being responsible for your database servers, and things like software engineering tools (git, shell scripting in general) are a few years off.

The number of databases I have seen out of source control is too many to count, the number of times I had people who understood SQL very well but couldn't use git worth a damn. Some of them have been modifying the top of the file of a stored procedure for decades

  2024-01-01 hobs - changed even more shit
  2023-07-24 hobs - minor tweaks
  2001-02-04 hobs - created

[ Parent | on HN ]

Re:Getting Your DBA Teams Scripts into Git by cafard on Wednesday July 03, 2024 @02:05PM (#40868509)

I am reasonably confident that Oracle keeps its code under source control, but the PL/SQL packages it supplied start with a lot of this. The package WWV_FLOW, central to the APEX/ORDS product has more than 500 lines like

  --    MODIFIED   (MM/DD/YYYY)
  --      mhichwa   08/04/1999 - Created
  --      mhichwa   09/30/1999 - Removed g_show_reset global
  --      mhichwa   10/09/1999 - Added g_last_query_text global for error reporting
  --      mhichwa   10/09/1999 - Removed g_success_procedure, g_success_url
  --      mhichwa   10/09/1999 - Removed g_step_sub_title_font_color   --
  --      mhichwa   10/14/1999 - Added 10 extra inputs v26 ... v35

[ Parent | on HN ]

Re:Getting Your DBA Teams Scripts into Git by hobs on Thursday July 04, 2024 @12:08PM (#40875962)

Thanks for the good laugh, but yeah, the time before source control is not that far behind some of us.

[ Parent | on HN ]