home.social

#dbadmin — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dbadmin, aggregated by home.social.

  1. Setup #fail2ban to stop some random IP from hitting my #postgres server again and again. It would never have been able to authenticate, but not going to let that keep happening.

    #selfhosting #dbadmin

  2. Do not run databases in containers, if possible - do not run them in virtual machines either. Databases love bare metal :sql:

    In fact, one evil red company even instructs bare metal deployment of their database for performance reasons :catroll:

    If you ever see container image of an application packed together with database - use it for development purposes only!

    You'll thank me later :blobcatfluffhappy:

    #sysadmin #dbadmin #virtualization #protip

  3. It may be common knowledge but my mind was blown. :amaze:

    We're using CentOS and my DBAD (Database Admin) instructor hinted at the option to make user input variables in some of the new dictionary views we learned this module and using WHERE name = UPPER('&NAME') in the select statement.

    I had no idea you could prompt for user input... I was in the middle of making 3 profiles, 9 roles,
    16 users, granting them roles and/or privileges as I went, editing a text file in gedit with the new user data and pasting it into the terminal.

    It may not actually be faster but it feels faster (I may be biased because I love database). The &UNLIMITED_QUOTA_TABLESPACE variable name is not the best and very long, use &QUOTA_TABLESPACE or something shorter, and the size can be changed to &SIZE_APPEND_M so you can enter 20M but we were using unlimited for the lab.

    #CentOS #Oracle #SQL #DBA #OracleSQL #Database #DBAdmin #DBAD #CentOS5 #Oracle12c

  4. It may be common knowledge but my mind was blown. :amaze:

    We're using CentOS and my DBAD (Database Admin) instructor hinted at the option to make user input variables in some of the new dictionary views we learned this module and using WHERE name = UPPER('&NAME') in the select statement.

    I had no idea you could prompt for user input... I was in the middle of making 3 profiles, 9 roles,
    16 users, granting them roles and/or privileges as I went, editing a text file in gedit with the new user data and pasting it into the terminal.

    It may not actually be faster but it feels faster (I may be biased because I love database). The &UNLIMITED_QUOTA_TABLESPACE variable name is not the best and very long, use &QUOTA_TABLESPACE or something shorter, and the size can be changed to &SIZE_APPEND_M so you can enter 20M but we were using unlimited for the lab.

    #CentOS #Oracle #SQL #DBA #OracleSQL #Database #DBAdmin #DBAD #CentOS5 #Oracle12c

  5. It may be common knowledge but my mind was blown. :amaze:

    We're using CentOS and my DBAD (Database Admin) instructor hinted at the option to make user input variables in some of the new dictionary views we learned this module and using WHERE name = UPPER('&NAME') in the select statement.

    I had no idea you could prompt for user input... I was in the middle of making 3 profiles, 9 roles,
    16 users, granting them roles and/or privileges as I went, editing a text file in gedit with the new user data and pasting it into the terminal.

    It may not actually be faster but it feels faster (I may be biased because I love database). The &UNLIMITED_QUOTA_TABLESPACE variable name is not the best and very long, use &QUOTA_TABLESPACE or something shorter, and the size can be changed to &SIZE_APPEND_M so you can enter 20M but we were using unlimited for the lab.

    #CentOS #Oracle #SQL #DBA #OracleSQL #Database #DBAdmin #DBAD #CentOS5 #Oracle12c

  6. Episode 101 - Devart's DbForge Studio will come out 1st of January 2022 at 5pm CET.

    Happy New Year to All of You

    Article:
    blog.tsr-podcast.com

    Audio:
    tsr-podcast.com

    #sql #dbforge #databases #dbadmin