As a database engineer, you can enjoy the high paying salary of a highly qualified professional. Database engineers have tough jobs, but the compensation makes up for it.
Being a database engineer can mean different things depending on the company you work for. If your company is new or is in a developing stage, than designing and creating databases from the ground up might be your daily duty.
If you're working with a company who has their databases in place, than your job might be troubleshooting issues with the database. The problems tend to not to be the actual database content, but usually in the design, how it is queried, or the software that interacts with the database.
A lot of times the database design can be improved upon. In these situations, it is sometimes better to start from scratch rather than fixing the problematic database. You will have to make the difficult decision of fixing or rebuilding the database. Your decision will usually have to get approved by your supervisor.
Dynamic reporting systems go hand-in-hand with database engineering. Sometimes you might be asked to build a dynamic reporting system or fix a problem with an existing one. This task usually comes up when the "numbers are wrong". Management wants them fixed and you have to figure out how these numbers are calculated in the first place. This can be very time consuming and hard to estimate the time of completion.
The hardest job about a database engineer is understanding all the software that interacts with the database. This could involve you picking up additional programming languages. This isn't necessarily too hard, but when you throw in deadlines, than this becomes a challenge.
The worst case scenario is you're brought into a situation, where you have to fix a major database and the previous database engineer named all the fields, queries, and tables weird names that you can't understand. Hopefully the previous engineer isn't retired and you can ask them questions. When you build a database, make sure you always build it in a way that the next guy will be able to understand the fields, queries, and tables.