question

Reporting Services itself is not much overhead. The problem comes with the heavy queries that are typically associated with reports. They usually have to process a lot of rows which means locking and blocking for relatively long periods. This tends to clash with the small quick queries that typically form most of the workload on an OLTP server. For this reason most people try to avoid installing Reporting Services on their OLTP server and instead use a separate server for Reporting. You also need an ETL (extract, transform, load) process to copy over the data needed. This can be once per night, every few minutes or somewhere in between. This does involve licencing both servers so it might be overkill. If you have a server with plenty of spare resources you could always try adding Reporting and see how it goes.