Is there a best practice for having separated an application and a SQL Database?
I am having a big problem, we have a COFIDI (A software for emitting invoices) application and the SQL database in the same server. The problem is that frequently,, the server stops due to memory saturation, and we have increased the amount of memory 3 times,, and every time the server takes all the memory. I know there is a best practice in the market for having separated these two components (application and SQL database). Can someone help me?
Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!