How to identify the SQL Version and SQL Edition

When working on AX implementations, one main purpose of Analysis phase is to identify and estimate the License costs for the Customer. And a major part of the Implementation cost can go into "Purchasing licenses"

During such a scenario, I found some helpful information on how to identify the Microsoft SQL Editions.

If you want to check the SQL Version and/or SQL Edition of the installed product, you can follow the below simple steps:
  1. Connect to the server in which SQL Server is installed.
  2. Open SQL Server Management Studio from Programs/Start. Alternatively you can type 'ssms' in Run.
  3. Connect to the Database
  4. Open a new Query window and paste the below code

    select @@servername
    go
    select @@version
    go
    select serverproperty('edition')
    go

  5. Execute the query


This will result in Three different output/resultset. The first provides you the "Name of the server", second provides you the "Version of Installed SQL" and the third provides you with the "Edition of SQL Server installed".

Couple more examples are as below:







Also you can find more details and Compare Editions, i.e, verify the features supported by different Editions of SQL in this Microsoft link: https://www.microsoft.com/en-us/server-cloud/products/sql-server-editions/overview.aspx 

Comments

Post a Comment

Popular posts from this blog

D365FO - Copy of databases across environments

Image
When working with Dynamics 365 Finance and operations implementations, it is an obvious step to perform database movements across environments. We have been doing this in the previous version (AX2012) as well, where we had to change the environments related settings after the database copy manually. Now we D365FO , we might end up in different scenarios based on the Tier-level of the environment . So I have tried to identify the #4 major scenarios in here and share the approach I have used.  Copy of DB from Tier 1 env. to another Tier 1 env. Copy of DB from Tier 1 env. to a Tier 2 env. Copy of DB from Tier 2 env. to another Tier 2 env. Copy of DB from Tier 2 env. to a Tier 1 env. The below picture is an illustration of different types and corresponding solutions on a high level (sorry for my not-so-good-handwriting 😅) #1 Tier 1 -> Tier 1 DB copy:   This scenario can happen quite common if you have multiple tier-1 environment in your on-going project li...
Read more

Extended Data Types in Microsoft Dynamic Ax & EDT array

Image
·          An extended data type is extended from a base type or another extended data type. The difference is that an extended data type has a property sheet where information such as labels, length and left or right adjustment are stored. ·          EDT are a central part of MorphX. Whether you are adding fields to a table or declaring variables from X++, extended data types should always be used instead of using base types and the reason for that is Dynamics Ax provides powerful features to handle EDTs. ·          The best practice is to check before creating a new extended data type you should check whether in existing one will fulfill your needs. ·          If you have found an EDT which suits your needs, but another label or help text is required, you should create a new EDT with your requirements, but never mod...
Read more

Error: Field 'xxx' does not exist in D365Ops

Image
Today I encountered a weird error while working with newly created Enums and Tables in Visual Studio 2015 with a Dynamics 365 for Finance and Operations project. Error message while trying to build my project was: The underlying type 'BKA_Status ' or its base type for table 'BKA_GoalMaster' field 'GoalStatus' does not exist. The underlying type 'BKA_GoalTypes ' or its base type for table 'BKA_GoalMaster' field 'GoalType' does not exist.</Message> However, I had the 'BKA_Status' as well as 'BKA_GoalTypes' Enums already available in my project and even the project is Synchronized with the database. Root cause: To be honest, I was unable to find the root cause for sure. However, I imagine the error has something to do with the refresh of metadata because of the kind of solution which helped to resolve the error.  I have had 'Extends' property filled in with another Enum which was not existing in t...
Read more