May 16, 2008 at 5:05 am
We are trying to assess on our infrastructure the counts of the various versions of SQL Server that we have.
The tool used will be able to look for executuables by name, e.g. SQLSERVER.exe, but that doesn't necessarily clarify what specific version of SQL Server is on a given Server/PC.
Is there any way to look for some identifiable file or executable to then better determine this sort of information? It can differentiate on executable size as well.
We are trying to distinguish between SQL Server 2000 and 2005 as well as Express, Standard and Enterprise editions.
Does anyone have any gem that might help here?
Thanks
May 16, 2008 at 5:40 am
The answer is no.
Different Editions of SQL server use the same install. You will also have major issues with figuring out the service pack of a particular server by just a file name or size.
You need to run: SELECT @@Version
I suppose you could write a procedure that generated a text file based on the server version and edition, but I think the real answer is that the tool you are using to collect the information you seek is not very good. Did you buy something that is supposed to be able to traverse your network and tell you something about your servers based on finding fales of a particular name? It seems like a horrible way to try to do software inventory.
May 16, 2008 at 5:54 am
The tool was I think written in house and it's real intent was a simple tool for all software.
Other products (not SQL Server), often use exe versions and other information that in a lot of cases are on a link between file name and file size. So knowing Product A with a 'standard' edition uses executable Z.exe of file size 1234KB where as an 'Enterprise' edition, uses the same (or different) named file of size 2468KB, helps get a quick ready-reckoner for the 'world'.
Thanks for the quick answer, I didn't think it was possible as is, but we can at least find all the kit using SQLSERVER.exe and then do a closer interogation of each knowing what they are.
May 16, 2008 at 6:29 am
"Other products (not SQL Server), often use exe versions"
SQL Server does use different file versions, your original post did not indicate that your tool could see file version information. You can tell SQL server version and service pack information from some of the individual files - although you will need to check multiple files.
If this is an in-house tool, I would recommend you have a developer modify it to simply connect to the SQL Server and run @@Version.
Or, go download a software inventory tool. You have an in-house tool that does not work all that well when there are hundreds of these tools that are inexpensive or even free.
Don't try to grow an apple when you can pick one from a tree.
May 16, 2008 at 6:54 am
If your in-house tool can use other tools then maybe SQL Scan could be used. It is part of the SQL Critical Update Kit and was provided to help identify instances vulnerable to Slammer, but you can just use it to scan your domain.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply