| Author |
Topic |
|
pszivos
Starting Member
10 Posts |
 Posted - 2005-10-19 : 05:29:48
|
Hello,We need to check the version of the MS SQL server installation with the MS SMS tool. I know it is possible to check it with the <select @@version>, but SMS cannot use it. Is there a way to judge it based on certain files (.dll's, .exe's etc) if the installation is a STANDARD or ENTERPRISE version? File size? version etc?The same we need to know for Analysys and Raporting services, too.Any help is most welcome,Peter |
|
|
schuhtl
Posting Yak Master
102 Posts |
Posted - 2005-10-19 : 09:02:04
|
| My company recently went through an internal audit of our sql server licensing and I contacted Microsoft and asked the same question. I was told that there was no way to determine the version based on files. |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-10-19 : 10:23:12
|
| The easiest way I now of is to look at the first few lines in the SQL Log files - that even has version differences like Standard / Developer which are hard to detect using @@VERSION type tests.Dunno if SMS could look at that?The file you need is called "ERRORLOG" and is usually located:x:\path\LOG\ERRORLOGKristen |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-10-19 : 13:07:36
|
| I think microsoft is wrong on this. ONe of the things to check is the version of the sql server executables itself. it is version 760 if you are at SP3, 2039 if you are at SP4, etc.In fact, I think this is the only reliable way to check the version of SQL becuase the internal objects could be patched up to SP3 or SP4 levels (what SELECT @@version tells you), but if the actual binaries are not patched up you are going to have a problem.-ec |
|
|
|
schuhtl
Posting Yak Master
102 Posts |
Posted - 2005-10-19 : 15:24:08
|
| eyechart,How does the executable version help determine if it is Developer, Standard or Enterprise edition? |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-10-19 : 16:05:31
|
quote:
Originally posted by schuhtl
eyechart,How does the executable version help determine if it is Developer, Standard or Enterprise edition?
umm, yeah. I see what you are getting at. Not just the version, but the release.If SMS lets you look at the registry, there is an Edition key that you can look at. This gets a little tricky to find if you have named instances though.Kristen's suggestion might be the best solution though.-ec |
|
|
|
pszivos
Starting Member
10 Posts |
Posted - 2005-10-20 : 02:56:46
|
| Thank you for everyone for the suggestions, but if we cannot judge the release by comparing any properties of a file we will do a very primitive solution:- run a script on each server and besed on the output of the select @@version we create a file named STANDARD or ENTERPRISE.- in every new installation the creation of this file will be part of the cookbook...Thanks again,Peter |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-10-20 : 08:49:21
|
I know this isn't exactly what you're looking for but it may be helpful.To get the service pack info for SQL Server you can do this:select SERVERPROPERTY('ProductLevel')SQLDiag gives a lot of good info too. Its in the binn directory of your SQL install.sqldiag -Usa -P[PASSWORD GOES HERE] -Oc:\SDOUT.TXT Daniel, MCP, A+SQL Server DBAwww.dallasteam.com |
|
|
|
Seventhnight
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2005-10-20 : 09:01:10
|
try looking in the "c:\windows" or "c:\windows nt" directory...there are 2 log files that have the edition and version. I believe they go with he current install.sqlsp.logsqlstp.logCorey Co-worker on children "...when I have children, I'm going to beat them. Not because their bad, but becuase I think it would be fun ..."  |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-10-20 : 14:46:08
|
| "if we cannot judge the release by comparing any properties of a file"So I'm curious to know why examining the files that I suggested doesn't work for you?Kristen |
|
|
|
|
How to check the MS SQL version by system files?