You can go deeper for instance by trying to find only instances of a certain version or edition and to sort the output. This basically works the same way as in a post I did earlier about how to get devices (network device, windows agents, unix/linux agents) out of SCOM through PowerShell. Throw the CSV file into Excel and you will have the data in clear format. Next we select for each DB engine the ComputerName (you could have used Path as well there), Instance Name, Connection string, SQL version (as a number) and SQL edition (Standard/Enterprise/Express). What happened is that we are looking for a class called SQL DB Engine and we pull in all instances of that class. $MyDevices | select | Export-CSV -notype C:\sqlinstances.txtĪnd Voila you have a text file with the required info. $MyDevices = get-scomclass -Displayname “SQL DB Engine” | get-scomclassinstance Now, lets pull this info into a CSV file using the Operations Manager Shell (these are two lines, enter as separate commands, and note these are SCOM 2012 commands): The state views here are nice and fast to find your instances of those as well. There is also Reporting Services for instance which is very common. Keep in mind that the SQL DB Engine is not the only possible SQL component which can be installed. It has the same information (could be you use the Personalize View actions item to add columns you are interested in). In the case of this management pack it is also possible to go to the Microsft SQL Server management pack folder to the left hand side and expand the server roles folder and select a state view, such as for database engine. Now you should get a list of all SQL database engines and their versions and names and lots of other information. Next find the SQL DB Engine and select it. Next on the right hand Actions Menu go for Change Target Type. So first thing I usually do for this and other reasons is to go in the monitoring pane all the way to the top in the left hand side menu and find Discovered Inventory. However if a SCOM agent is installed and the SQL management packs are imported they will discover the SQL component and put some info in the discovered inventory for you. There are tools like SCCM and SCSM for those kind of things. The first thing to understand is that SCOM is not a CMDB. SQL Data Compare helps you compare and deploy changes. Damaged or missing data can be restored to a single row, without the need for a full database recovery. You can work with live databases, backups, or SQL scripts in source control. Sometimes as inventory, sometimes to find instances no longer supported, rogue instances, needed for licensing info and so on. SQL Data Compare is the industry-standard tool for comparing and deploying SQL Server database contents. What about MSSQL10.SQLEXPRESS? Why it doesn't have mssql.4 number? MSDN says that it's a sequential ID of installed components.I often get questions for getting SQL info together, such as names, instances, versions, editions and so on for all kinds of purposes. It seems that the only way to find what versions are installed (besides regedit) is by the Sql Server Configuration manager.ġ) Is it possible by file system only, to detect what versions I have installed?Ģ) Is there any other way (besides registry), to see what SQL versions installed?ģ) I read that mssql.1 is for the engine. I've attached a print screen for my sql server folders. I want to see all of the versions - if installed!Įxample: a computer can have sql 2000, 2005, 2008 ,2008R2 If I'm running a query and typing : select tells me the running thread version. I want to see what versions of sql are installed on my computer. How can I determine installed SQL Server instances and their versions?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |