Skip to main content

Upgrading SQL 2008 R2 Edition – Step by Step Guide

Please follow below steps for upgrading a SQL 2008 R2 edition. This example shows an upgrade to Enterprise edition but the steps are exactly same for any valid upgrade scenario.

Step 1: 
Arrange the media on an accessible location from the server. Also arrange a downtime of 15 minutes as you will need to restart the SQL Services to make the upgrade effective.
Step 2: 
Before upgrade, make sure to take a final backup of the databases and stop the applications as per standard protocol to eliminate any risk of data loss in case of a failure.

Step 3: 
Execute setup.exe from media. It should lead you to below screen:

Step 4: 
Select Edition Upgrade from Maintenance Tab

Step 5: 
Click ok at next prompt assuming you passed the setup support rules.

Step 6: 
Select Next at this step.

Step 7: 
Select Next. If you are using volume licensing then product key should be populated. Otherwise you need to enter a valid product key for upgrade.

 Step 8: 
Accept license term and select Next

Step 9: 
Identify instance to be upgraded and select Next

Step 10: 
Select next after all Edition Upgrade Rules are passed.

Step 11:
Review the final setting and then hit Upgrade.

Step 12: 
After you hit Upgrade, SQL Server Edition will be upgrade to Enterprise.

Please note below points which may be useful while working on a Production Environment:

  1. For a typical machine (at least 16 GB RAM with 2 Physical CPU), this upgrade should complete with in 10 minutes. However this time may widely vary on your server’s configuration and hardware.
  2. You must restart SQL Services to make the change effective.
  3. You do not need to execute any special step even if the instance is clustered.


Anonymous said…
Your blog is really helpful to me.
Anonymous said…
Yes, very helpful. Thanks dude!!!!

Popular posts from this blog

How to kill a negative SPID (like SPID -2) in SQL Server?

Rarely this scenario will arise when most likely you see this negative SPID (most likely SPID -2) is blocking other transaction causing issues. If you try to kill it using normal KILL command, it will fail reporting below error: Msg 6101, Level 16, State 1, Line 1 Process ID <SPID Number> is not a valid process ID. Choose a number between 1 and 2048 This is because of an orphaned distributed transaction ID.  Please follow below steps to kill it: Step 1: -- Find the UOW Number select req_transactionUOW from master..syslockinfo where req_spid = <SPID Number> --  <SPID Number>  is -2 most likely. Step 2: -- Copy the UOW number from Step one KILL ‘<UOW Number>’ This will kill the negative SPID resolving the issue.  However please note following points: 1. For SPID -2, you may find multiple UOW numbers. Please start killing them one by one. Typically killing first UOW will resolve the issues. (ie. will kill all UOW and release

DMV/TSQL to find out basic hardware information of the SQL Server including when SQL Server started.

Please use below code: However, please be advised that it can not tell correct information around virtualization.  For example, it will show Hypervisor even if SQL runs on a physical OS where Hyper-V is on. So use this query only when you do not have sufficient access on underlying Windows Operating system to get these information directly. -- Basic hardware information for SQL Server (sys.dm_os_sys_info) /* This query is courtesy of All credits goes to original author. */ SELECT cpu_count AS [Logical CPU Count] , scheduler_count , hyperthread_ratio AS [Hyperthread Ratio] , cpu_count / hyperthread_ratio AS [Physical CPU Count] , physical_memory_kb / 1024 AS [Physical Memory (MB)] , committed_kb / 1024 AS [Committed Memory (MB)] , committed_target_kb / 1024 AS [Committed Target Memory (MB)] , max_workers_count AS [Max Workers Count] , affinity_type_desc AS [Affinity Type] , sqlserver_start_time AS [

‘Trace Skipped Records’ – What is this and how to resolve it while using SQL Server Profiles?

In some very rare case, you may experience a very weired message in profiler’s output as ‘Trace Skipped Records’ while you trace something on SQL Server. Screenshot of similer situation is as below: This is not an error but it comes by design of SQL Server (I believe so). When you are using SQL profiler and return data is too big to fit in the GUI (for me, it is an enormous xml), SQL Server simply prints this message and proceed to next step. Mostlikely this is to save server’s memory and performance. Although not suggested and guranteed, you can try to run a server side trace and dump data in a file which should capture all the data. However, it is strongly not recommended to run a trace on your production server from server side. Microsoft will probally document this limitation in future. More details may be found at