Determine your SQL Server Version, Service Pack, and Edition

To determine the version of SQL Server, you can use any of the following methods:

Method 1

Connect to the server by using Object Explorer in SQL Server Management Studio. 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 SQL Server.

Method 2

Connect to the instance of SQL Server, and then run the following query:

Select @@version

An example of the output of this query is as follows:

Microsoft SQL Server 2008 (SP1) – 10.0.2531.0 (X64)   Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

Method 3

Connect to the instance of SQL Server, and then run the following query:

SELECT SERVERPROPERTY(‘productversion’), SERVERPROPERTY (‘productlevel’), SERVERPROPERTY (‘edition’)

Note This query works with any instance of SQL Server 2000 or later

The following results are returned:

• The product version (for example, 10.0.1600.22)
• The product level (for example, RTM)
• The edition (for example, Enterprise)

For example, the results resemble the following:

10.0.1600.22 RTM Enterprise Edition

Note The SERVERPROPERTY function returns individual properties that relate to the version information, although the @@VERSION function combines the output into one string. If your application requires individual property strings, you can use the SERVERPROPERTY function to return them instead of parsing the @@VERSION results.

VERSION INFORMATION

SQL Server 2012 version information

The following table lists the major releases of SQL Server 2012:

Release	Product Version
SQL Server 2012 Service Pack 1	11.00.3000.00
SQL Server 2012 RTM	11.00.2100.60

SQL Server 2008 R2 version information

The following table lists the major releases of SQL Server 2008 R2:

Release	Product version
SQL Server 2008 R2 Service Pack 2	10.50.4000.0
SQL Server 2008 R2 Service Pack 1	10.50.2500.0
SQL Server 2008 R2 RTM	10.50.1600.1

SQL Server 2008 version information

The following table lists the major releases of SQL Server 2008:

Release	Product version
SQL Server 2008 Service Pack 3	10.00.5500.00
SQL Server 2008 Service Pack 2	10.00.4000.00
SQL Server 2008 Service Pack 1	10.00.2531.00
SQL Server 2008 RTM	10.00.1600.22

SQL Server 2005 version information

The following table lists the major releases of SQL Server 2005:

Release	Product version
SQL Server 2005 Service Pack 4	9.00.5000.00
SQL Server 2005 Service Pack 3	9.00.4035
SQL Server 2005 Service Pack 2	9.00.3042
SQL Server 2005 Service Pack 1	9.00.2047
SQL Server 2005 RTM	9.00.1399

SQL Server 2000 version information

The following table lists version number of the Sqlservr.exe file:

Release	Product version
SQL Server 2000 Service Pack 4	8.00.2039
SQL Server 2000 Service Pack 3	8.00.760
SQL Server 2000 Service Pack 3	8.00.760
SQL Server 2000 Service Pack 2	8.00.534
SQL Server 2000 Service Pack 1	8.00.384
SQL Server 2000 RTM	8.00.194

For more information, please refer to Microsoft KB321185 – How To Identify your SQL Server Service Pack Version and Edition.

Ref : lumension

How to Identify the Version and Service Packs installed on a SharePoint 2013 Server

In many cases, we may not be bothered about the Version, Service Packs installed on our Server when we do the development. It is obvious that, when we get the requirement, immediately we will start analysis the requirement.

But recently there was a situation that one of our client wants to move on to the new Service Pack which released on this April. In that case, we may also have to analyze the impact of the new Service Pack. Before knowing that, I just wanted to know, what are the things installed on our Dev environment first. Then on top of it, what needs to be installed and what would be the impact after installation.

To answer all these questions, First we need to know what is the version installed on our Farm. Use the following command to get the Version of the product installed using PowerShell script.(Get-SPFarm).Products.

First Run ISE as below :

Then after selecting the Commands of “Add.PSSnapin” output of the above command will be something like,

By seeing the GUID, we will be able to identify the Product. These GUIDs will not change. On all the environments, and all the machines, the GUIDs will remain same.

Here are all of the product GUIDs:

GUID : 35466B1A-B17B-4DFB-A703-F74E2A1F5F5E Product : Project Server 2013

GUID : BC7BAF08-4D97-462C-8411-341052402E71 Product : Project Server 2013 Preview

GUID : C5D855EE-F32B-4A1C-97A8-F0A28CE02F9C Product : SharePoint Server 2013

GUID : CBF97833-C73A-4BAF-9ED3-D47B3CFF51BE Product : SharePoint Server 2013 Preview

GUID : B7D84C2B-0754-49E4-B7BE-7EE321DCE0A9 Product : SharePoint Server 2013 Enterprise

GUID : 298A586A-E3C1-42F0-AFE0-4BCFDC2E7CD0 Product : SharePoint Server 2013 Enterprise Preview

GUID : D6B57A0D-AE69-4A3E-B031-1F993EE52EDC Product : Microsoft Office Web Apps Server 2013

GUID : 9FF54EBC-8C12-47D7-854F-3865D4BE8118 Product : SharePoint Foundation 2013

And to know about the Service Packs, there is no need of any PowerShell Commands. That we can directly go to the Central Administration and find.

Go to Central Administration.

Click on “Upgrade and Migration” on the Quick Links.

Click on “Check Product and Patch Installation Status”

This will tell us the current Patches Installation. By seeing the Version column we can identify. On the screen shot above shared, there is no SP installed.

Delete All Old Versions from SharePoint 2010 Document Libraries

How many versions of a typical document do you need to keep?  5?  10?  100?

SharePoint content databases often get cluttered with redundant versions of the same documents.  In some cases, I’ve seen presentation libraries with less than 10 GB of active content, but hundreds of GBs of content due to gradual changes.

If you’re ready to clear out old versions, SharePoint 2010’s Management Shell makes it easy.  The script below will iterate through all lists and update them to keep only the last 2 copies.  It will also loop through and delete unneeded versions.

Get-SPWebApplication |  Get-SPSite -Limit All |  Get-SPWeb -Limit All |  ForEach-Object  { ForEach($list in $_.Lists) { If($list.EnableVersioning -eq $true) { $list.MajorVersionLimit = 2; $list.Update(); ForEach($item in$list.Items) { $item.URL; $item.SystemUpdate() } } } }

You can see that it…

1. Loops through all web applications
2. Loops through their site collections
3. Loops through their webs
4. Loops through their lists
5. If versioning’s enabled, it sets the major version limit to 2
6. In order to remove old versions, it needs to loop through each item and perform a system update

The script can be easily amended to deal with only specific site collections / libraries.  To keep a different number of versions, modify the MajorVersionLimit variable above.