What to build a client-database chain from if you are new to programming and you need it for a scientific project (helth risk/environmental risk)?

Question

Database

Good afternoon.
There is a scientific project of its own, which is focused on predicting risks to human health. It already has some array of data, logical expressions and formulas. I got a burning desire to automate everything and instead of Excel and Statistics go to the level of automation - that is, make an application that will pull information from the server (in fact, the site is hosted) and build a forecast.
With the language for the application, the choice is in Python (I know it a little + I already have experience in writing programs).
But with the second part of the problem, since in terms of the database and DBMS, how to configure them, connect, host and everything, everything - I'm 0!
Please help me decide on my course of action - what to study and what to build on.
Questions:
1- It is clear that SQL, it is not clear which DBMS to use and through what to administer it (according to the proposed DBMS, I will study the sources)
2- Actually, if possible, suggest what to learn and what to rely on.
3- How to correctly connect the client application and data in a remote database - a permanent Internet connection or a daily update of data on the client version.
4- How to choose the right hosting for the site for these purposes and what to look for.
Thank you for your attention and your answers.

Answer 1

1. Why did you choose relational databases? There is a NoSQL DBMS, for example - MongoDB. I advise you to consider. If, in principle, there is little experience in working with databases, then it will be easier to enter MongoDB, as it seems to me. It all depends on the amount of data, whether the scheme is known in advance and what the loads will be. If this is a small project - I would advise you to take monga. If the choice, for some reason, falls on SQL - the most clumsy - MySQL. When working with the database for administration, the IDE from JetBrains is enough. If you need a more understandable panel - phpMyAdmin
2. Depends on what you choose in the 1st paragraph. There is an excellent book - "7 databases in 7 weeks". There are sections on both SQL DBMS and NoSQL DBMS. The book is from the category of review, but there is enough information to start working at the initial level. Each chapter is read in a few hours, so I advise you to watch it.
3. Why should the database be remote? In the first couple, it will be easier for you to throw the base next to the application. If the application needs to receive any updates, run a script every n-hours that will pull this data from a remote server. Pass data for update - many ways, depends on the situation. I would advise to look towards message brokers, ala RabbitMQ. But after you've done the rest.
4. What load will you have? Too many unknowns to give any answer.