Microsoft SQL Server comes with a very powerful configuration manager which can be used to manage the SQL Server services and control network visibility and footprint. Working without the SQL Server Configuration Manager is a nightmare for a DBA.
SQL Server Configuration Manager is not available in Windows 8
Many development environments have SQL Server installed on the developer workstations running a Windows 8 operating system. I have been consulted on a couple of instances where the SQL Server Configuration Manager fails to come up in the “Start” menu application list (even using the Search charm does not yield any results).
The workaround
The SQL Server Configuration Manager is in reality a Microsoft Management Console (MMC) application. Hence, the workaround is to do the following:
- Launch the Search charm
- Search for the SQL Server Configuration Manager MMC snap-in:
- SQL Server 2012 – search for “SQLServerManager11.msc“
- SQL Server 2008R2 – search for “SQLServerManager10.msc“
- Press “Enter” to launch (or alternatively, right-click on the result to pin to the Start Menu or create a shortcut on the desktop)
Further Reading on the SQL Server Configuration Manager
- SQL Server Configuration Manager – Hide your SQL Server Instance [Link]
- #0151 – SQL Server– Which TCP/IP port is my SQL Server listening on? [Link]
- Changing SQL Server Service Account or Password – Avoid restarting SQL Server [Link]
[EDIT, 09/08/2014, 10:55AM IST]: Rectified a typo for the MSC file name related to Configuration Manager for SQL Server 2008 R2.
Until we meet next time,
You wrote
“2.Search for the SQL Server Configuration Manager MMC snap-in: •SQL Server 2012 – search for “SQLServerManager11.msc“
•SQL Server 2012 – search for “SQLServerManager10.msc
”
It is possible that there is a little error ( or maybe , with my poor understanding of the English language , I have not understood what you wrote )
SQL Server 2014 ==> version 12
SQL Server 2012 ==> version 11
SQL Server 2008/2008 R2 ==> version 10
I think that SQLServerManager10.msc is for 2008/2008 R2
For SQL Server 2014 , I suppose that we have to use SQLServerManager12.msc
LikeLike
Hello, Patrick!
Thank-you for taking the time out and reading my post. Also, many thanks for pointing out the typo! I stand corrected – I have fixed up the error and updated the post.
Once again, many thanks for your valuable feedback!
LikeLike
Pingback: #0405 – SQL Server – Msg 5133 – Backup/Restore Errors – Directory lookup for file failed – Operating System Error 5(Access is denied.). | SQLTwins by Nakul Vachhrajani