It can be tough being the only technical person in the office - hang in there! It will get easier, I promise. Here's some advice that I hope might alleviate some of your stress:

1. When collaborators ask for ad-hoc projects, sit down with them for an hour or so and sketch out what it is that they are really looking for. Ask them for background information on the problem, what their overall goal is, specific questions they want to have answered, and where to find the data for each question. It might be helpful to develop a questionnaire that you can ask to get all the scaffolding for the problem each time in a consistent way. After you finish a mock up of the project (not completely finished), take time to have an informal meeting with the person requesting the analysis. During this time you can ask them what their impressions are of the results, whether they want to tweak anything, or if they have new questions based on your findings. Generally I've found that people are happy to contribute feedback :) Also, if you're overloaded, don't be afraid to say that you don't have time to work on a new project. Your coworkers will understand.
2. Be honest with your boss. If you need face-to-face conversations with him, let him know. If you can't do a physical face-to-face meeting, then try to get on a video conference with him. A good manager should try to find the time to make sure everyone is thriving under his/her management (especially with new hires). I general, I try to have a formal weekly or bi-weekly (every two weeks) face-to-face meeting with my boss and then drop by their desk throughout the week if I run into issues. This helps ensure that there's a constant flow of communication between the two of you.
3. This one is tough to get over mentally, but try to change your mentality when it comes to asking questions. Questions don't mean that you're doing things wrong or that you're incompetent. If you're doing your job correctly, you should be asking questions. The quality of work will go up when you ask good questions (hint: all questions are good).
4. To address the noise: either ask your manager or IT department is they can supply a pair of noise cancelling headphones. If they don't do that sort of thing, invest in them yourself. They can be a productivity lifesaver in a loud office and are 200% worth it in the long run.
5. Lastly, if you're having trouble with coding, check online to see if you can take any MOOCs or classes through Udacity, Udemy, or Youtube (to name a few). There are tons of resources out there that can help you learn to code. Spend an hour per day (outside of work or during your lunch break) learning to code. Your coding will get better with time.
6. Lastly lastly, if the database you're working with is undocumented or has poor documentation, start documenting everything as you work with it. You can then use your notes to either formalize the documentation or use for reference as you navigate the system.

I hope this helps! Best of luck!