How can I check what all SQL server features and version are installed on my Machine ?
It’s a frequently asked question. You need to study your environment, need to login each instance to check version & other details, to answer this question.
Till SQL Server 2005, you have no direct solution.
But Starting from SQL Server 2008, Microsoft added a SQL Server discovery report as an useful tool under Tools page of Installation Center.
SQL Server Discovery tool
Lunch SQL Server Installation Center under Configuration Tools ( Click on the Start menu, go to All Programs, click to Microsoft SQL Server <Version Name>, under Configuration Tools click on SQL Server Installation Center) OR Directly Run Setup.exe & browse to Tools Page
Step 1
Step 2
Step 3
Report will be generate & open in default browser automatically
Report Location
The SQL Server Discovery Report will be saved automatically in %ProgramFiles%Microsoft SQL Server100Setup BootstrapLog<last Setup Session>
Other Useful Options
· You can also generate the Discovery report through the command line. Run “Setup.exe /Action=RunDiscovery” from a command prompt
· If you add “/q” to the command line above no UI will be shown, but the report will saved in %ProgramFiles%Microsoft SQL Server100Setup BootstrapLog<last Setup Session>
Limitation
· SQL Server discovery tool cannot be used to discover Remote SQL server installation
If you liked this post, do like on Facebook at http://www.facebook.com/mssqlfun
Reference : Rohit Garg (http://mssqlfun.com/)
I read your articles everyday and i must
say you have high quality posts here.
Hello,
Am trying to run the Installed SQL Server features discovery report. When I click on it there is no report generated. A small window briefly flashes and disappears. Also, no report can be found in %ProgramFiles%Microsoft SQL Server100Setup BootstrapLog. Any assistance is appreciated. Apologies if this is not the correct location to post this inquiry.
James
You can run the setup and can find it.
In case it’s not coming, Share installation logs. Also check windows event logs for related errors.