At my company I recently joined, there is one main person who understands the database schema. There are many tables and many fields, and it is not at all intuitive what many of these mean. Therefore, when somebody needs to make any sort of not-common query in the databases, we ask this person.
I am supposed to have something done today that involves getting a result from the database that I don't know how to get (I am a software developer, and I know SQL and can figure out other query languages, and I have access to the database, but I and others beside him just don't understand the schema and how the fields are used). On Friday, the database person was busy, yesterday he took the day off, and today he still hasn't responded to my Slack messages.
What do I do, and how do I prevent these sorts of situations in the future? This is my first full-time job, and so far it is often the case that my work depends on other people, and it has hard get these dependencies resolves, despite contacting them in advance. Plus, it feels frustrating because I don't think many of these dependencies should exist in the first place! Why not just have a one-page document that describes the unknown and confusing parts of the database? I would build this document myself, if I could actually get a long meeting with the database person scheduled.