Skip to main content

Installing SQL Server Denali CTP 1 – A step by step guide

Please refer to this post for step by step installation guide of SQL Server Denali (possibly SQL 2011) with screen prints. However please note that this is an installation from CTP1 as available at as of now. Future release or final release may not be exactly same but should be very similer.

Step 1: Select the installation type. (I am selecting New SQL Server Standalone installation)

Step 2: Setup should pass all the setup support rules. Then click OK to proceed.

Step 3: Install Setup Support Files by clicking on “Install” button.

Step 4: Setup should pass setup support rules. You may ignore warnings and go ahead based on case to case basis. Click Next to continue.

Step 5: Select Edition or specify the key. (For volume licensing, key should be auto populated in released versions). Here I am selecting Enterprise Evaluation here. Click Next to continue.

Step 6: Accept license terms and click Continue. Decide if you want to send the statistical data to Microsoft and check the relevant box appropriately.

Step 7: Select Feature Role. I am selecting SQL Server Feature Installation. Click Next to continue.

Step 8: Select the features you want to install and modify shared feature directory path if needed. Then click Next to continue.

Step 9: In next screen, it should pass all the installation rules. You may want to ignore some warnings if appropriate. Click Next to continue.

Step 10: Configure instance level details like selecting default instance or name an instance. Also customize instance’s root directory if required and then click Next to continue.

Here I specified D:\SQLDenali as instance root directory and installing default instance.

Step 11: Drive space should be available for the installation. Then click Next to continue.

Step 12: Give details at Server configuration page. (Give credential on which services should run and change the server (SS and AS) coalition if required). Then click Next to continue.

Here I am darkening the service account details I am using for this installation for security purpose.

Step 13: Complete the database engine configuration and click next. Make sure to add the initial administrative member of the server and customized default data directories. Click Next to continue.

Here I added my account to continue but intentionally darkened it.

Step 14: Complete similar configuration for analysis service and click next.

Note: Here again I added my account as administrator and darkened it.

Step 15: Define how you want reporting service to be installed. Here I am choosing “Install the native mode default configuration” as I want SSRS instance to be usable immediately after the installation is complete. Then click Next.

Step 16: Define if you want to send data to Microsoft and then click Next to continue.

Step 17: Installation configuration rule should be passed. Then click Next to continue. You may want to ignore some warning if it is suitable for you.

Step 18: AT this stage, everything is ready to install. Review the configuration and then click Install to continue.

Step 19: Grab a cup of coffee while the installation is complete.

Step 20: After the installation is complete, you should see the installation status as success. You may want to review the log from the GUI only to review the log. Click close to stat playing with Denali.

Now you have SQL Server Denali up and running on your machine for your first look. Also you do not have to reboot your server after this installation is complete.

NB. If you have .net framework version only up to 3.5 SP1 installed on your server or does not have powershell 2.0 installed on your server, you will face issues with installing Denali. Please refer to below posts for the resolution of such issues:


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