Tools and best practice for reporting/presentation database Currently my employer has a team that creates tableau dashboards and another very large team that creates ad hoc and regular reporting for external clients.
Both of these teams pull data from many databases and other sources.  For each report they either create a script that lives on their machine, a stored proc that lives in a source database, sometimes a scheduled job on a jenkins instance, or manually copy and paste the results of a query.  It's a badly documented mess.

My solution, that will have the least impact on how they work, and cost to implement, is to create a database on which all of the extracted data will live, so the reports and dashboards only access this single source.  A task scheduler to run regular extraction jobs, and a fairly simple custom software application that tracks changes to the source databases and alerts the project owners (of the jobs) but can also be used by the database owners to determine which downstream jobs will be impacted by changes to their databases.

I was wondering if what I have described already exists as a concept (is a presentation database a thing?) or if there exists software that could do the bulk of the heavy lifting for me? I after any tools that I might look into as alternatives, or concepts that might help my better design this solution.



So data needs to be extracted mainly from mssql, jira, jenkins and few custom sources.  I'd be storing the extracts on RDS and running the jobs once migrated on Jenkins.  I'd be building a custom web based UI for some very specific interactions, but monitoring would all be tableau dashboards.  

The RDS instance wouldn't be a true data warehouse or vault, more akin to a lake I guess, as the data stored there would be aggregated from the disparate systems for a very specific purpose per table and would not be linked to each other in anyway.  This is basically replacing a huge number of regular extracts living all over the various systems and disks and instead storing them in a single database. 

So I'm wondering in particular if this setup is common? and if there are any tools I should be looking at that might do some of this already.
It seems you are referring to a concept called a data warehouse.  Data Warehousing is a huge topic, with a few main types of architecture: star schema, snowflake, and data vault. Googling these might give you some ideas on how to proceed.