If you encounter this error during Security Compliance Manager setup, don't rush into creating a dedicated SQL Server instance (which could be a solution indeed, but try this simple tip first) - probably the only thing you have to do is to enable Named Pipes and TCP / IP in SQL Server Configuration Manager.