Determining sql server edition

Method 2: Look at the first few lines of the Errorlog file for that instance. The entries may resemble the following:. This entry provides all the necessary information about the product, such as version, product level, bit versus bit, the edition of SQL Server, and the OS version on which SQL Server is running. The output of this query has been enhanced to show additional information, as documented in the blog post article, What build of SQL Server are you using?

The output of this query has been enhanced to show additional information. This tool gives information about all the instances of SQL Server that are installed on the system. The only thing to be aware of is that this tool can be run locally only on the system where SQL server is installed. It cannot be used to obtain information about remote servers.

To determine which versions of the client tools are installed on your system, start Management Studio, and then click About on the Help menu. See the following screenshot. The version is also displayed in the Reporting Services Configuration tool. After Object Explorer is connected, it will show the version information in parentheses, together with the user name that is used to connect to the specific instance of Analysis Services.

Method 2: Check the version of the Msmdsrv. The default locations are shown in the following table. For more information about verifying Analysis Services build versions review Verify Analysis Services cumulative update build version. Because replication agents may be installed on several different computers, it is important to check the installed versions on all affected computers.

For example, the Distribution Agent in Transactional or Peer-to-Peer replication may exist on computers that differ from the publisher instance of SQL Server and may exist on the various subscriber instances of SQL Server in a pull subscription. Therefore, you have replication agent files that are installed on the IIS web server. And you may have to check the version of those. For more information, see Upgrade or patch replicated databases. Except for Sqlservr.

The versions of these files will change only when there is a fix to the respective component. Generally, you can check the file version of each of these. The highest version in the list is the version of the full-text search component that is installed on the system. You can use one of the following methods to determine the version of the full-text search component that is installed on your system. Each of these methods may indicate that the version of the full-text search component is either RTM or a version that is earlier than the current version of the database component.

We acknowledge that this is a problem and are working on fixing it in a future update. In this example entry, the third line Patchlevel indicates the current build of full-text search component that is installed, and the fourth line Version usually shows the original version of full-text search that is installed.

Method 3: Use the Summary. The following registry subkey shows the binary versions that are installed on the SQL Server. However, this version does not necessarily match the website and database schema version until the MDS upgrade process is complete.

You can check the installed product version and schema version by using the following query in the MDS catalog:. That's it, we are done, these were some of the widely used ways to check version of SQL Server. Ask a question Contribute an article Questions Articles. Checking SQL server version using various methods Now, I will explain possible ways to determine sql server version and service pack, let's get started with it. Login or Register to comment.

Related Articles Top SQL tips for beginners a must read. Related Questions Could not find stored procedure. Active Oldest Votes. Improve this answer. Vijay Vijay 3 3 bronze badges.

Unfortunetaly production servers are as bare as possible, mearning all kinds of residiual stuff has been removed for security purposes. Shanky Shanky Apparently OP does not have access to Registry Yes I have read that and I have mentioned that in my answer it scans the registry, but I wanted him to try anyways.

I am not sure who downvoted may be he lacks appreciation and knowledge, in the answer it is also mentioned that please see SQL Server installation summary. Shanky Thanks for the additional suggestions, but to futher complicate things, our production server have all unnecessary stuff removed for security purposes.

Which means that the summary stuff and the setup have been removed. Which means I can't run the discovery tool. While "getting SQL Server access" would be a seemingly easy choice, it isn't in our environment. Noone's going to give me permissions to thousands of hosts just so I could check if they have an SQL Server installed and if yes, which Edition. Ramil so you want to say that even the installation logs have been removed as well?.

I was trying to say that if some one wants to get SQL Server inventory a simple read access would not harm but since I do not know much about the security so I will not comment much. I would still suggest you to ask for this, this will save both yours and clients time — Shanky.

Show 1 more comment. The Overflow Blog.