IS and TN DB - Separate

I’m building out the environment and create separate databases to store the IS and TN schemas. Just wondering if anyone think that’s a good idea or just more overhead and unnecessarily maintenance.

It is not a overhead to have IS and TN separated in different schemas. For example, if your volume of transaction is huge, your TN would need more space compared to IS.

-Senthil