SharePoint - should I make it a seperate instance on an existing SQL Server?
Posted on 2015-01-19
We will deploy the latest SharePoint Foundation (60+ users) but we do not know if we should make a separate instance for SharePoint on our existing SQL Server 2008 R2 to save SQL licensing or buy a new SQL Server dedicated to SharePoint which can cost quite much.
At this moment, our existing SQL Server 2008 R2 is only used for our business critical ERP software (20+ users). The ERP databases have confidential financial data. If we make a separate instance for SharePoint, we are concerned that the SharePoint admin/programmer will get into them, as he would like to have local admin privilege to the server running SQL Server 2008 R2.
Also, we are concerned that his work (development, testing, administration) on SharePoint may affect our ERP software which is very critical for the business.
I am wondering if anyone has experienced the same dilemma as us? Or maybe we should simply spend some money to get a new dedicated SQL Server for SharePoint?