Common Database Issues


Connectivity Issues

  • Might be able to log in, but cannot connect to the database despite being logged in
    • might get error that machine can’t connect or that you’re blocked
    • may need to add IP to the approved list
  • Can’t see the database at all
    • could be due to a problem with permissions
      • IT may need to add you to the security group for access
  • When your data is connected through APIs and web-based systems, your connection may break due to
    • firewall rules
    • DHCP/DNS reconfiguration
    • and more

Capacity Issues

  • system is taking a long time to either pull data up or let you put data in
    • first action you should take is to check your internet speed
      • If it is within normal range, you could have a capacity problem
        • Excessive load time can occur if the system you’re working in has reached capacity
        • Sometimes systems reach their caps because of inefficient queries or inefficient infrastructure
        • When troubleshooting excessive load time, you should consider both of these reasons for a system to reach maximum capacity
  • your duty to report any performance issues you are experiencing and suggest possible causes
  • If you are experiencing excessive load time,
    • it’s possible that changes in capacity were not taken into account during change management

Capacity planning is a practice which involves estimating the personnel, storage, computer hardware, software, and connection infrastructure resources required over some future period of time.

Inefficient Queries

  • system starts to run slowly after you create a new query or a new data model,
    • first step should be to check your queries and make sure they are running correctly
      • go back to the source when doing so
    • the capacity of the servers should also be a consideration
      • especially if the queries appear to be running properly

Refresh Issues

  • if user reports that the data is not up to date, it could be that it failed to refresh
  • When troubleshooting this issue,
    • start with the connections in reporting tools (such as SQL, PowerBI, Tableau, etc.)
    • determine the refresh interval of all the data sets involved to ensure everything is set to refresh at a good rate
    • use monitoring/logging tools to troubleshoot broken or slow reports
    • human in the loop may be holding up the process

Scheduled Change

  • all changes should occur during maintenance windows
    • unless emergency
  • changes should be planned and tested in a test environment prior to being implemented in a production environment
  • After a change has been implemented,
    • its impact should be assessed
    • process reviewed and documented to identify any outcomes that could help future change management projects
  • If you are unable to find another reason for a slowdown,
    • check whether maintenance is occurring