If you attended my SharePoint Conference Session on SharePoint 2010 on SQL Server Denali you’re probably ready to get started with some of the features and capabilities we discussed and demonstrated today, particularly AlwaysOn Availability Groups which provide a robust, ready to use solution supporting both local redundancy and remote disaster recovery.
SharePoint 2010 is not currently supported on SQL Server Code Name “Denali”.
There are several prerequisites to using AlwaysOn which are documented further at http://msdn.microsoft.com/en-us/library/ff878487(v=SQL.110).
Windows Server Failover Clustering
While SQL Server Denali does not need to be clustered from a SQL Server perspective, the nodes on which SQL Server Denali is installed should be members of the same WSFC if configuring an AlwaysOn scenario.
The steps in this post make several assumptions about the SQL Server environment where SQL Server Codename “Denali” will be installed. The steps to install and configure SQL Server Codename “Denali” may differ as a result.
These steps will help you configure AlwaysOn in a SQL Server Code Name “Denali” environment.
Download SQL Server Code Name “Denali” CTP3
Download SQL Server Code Name “Denali” CTP 3.
Download SQL Server Code Name “Denali” CTP3 at the TechNet Evaluations Center.
Create or Select a Windows Server Failover Cluster
Choose and existing or create a new Failover Cluster on which each node SQL Server Code Name “Denali” will be installed.
Install .NET Framework 3.5.1
On each Windows Server where SQL Server Code Name “Denali” will be installed install the .NET 3.5.1 Features.
Install SQL Server Code Name “Denali” CTP3
Install SQL Server Code Name “Denali” CTP3. For installation instructions see also Installation for SQL Server ‘Denali’.
Enable Named Pipes and AlwaysOn High Availability Groups
Enable Named Pipes and AlwaysOn High Availability Groups.
Enable Named Pipes
MSSQLSERVER will need to be restarted to commit the changes.
In SQL Server Code Name “Denali” you will need to include the startup option 9532 (TraceFlag 9532) to enable enabling AlwaysOn High Availability Groups. To configure the required startup option on each Windows Server where SQL Server Code Name “Denali” is installed:
Enable AlwaysOn High Availability Groups
The Windows Failover Cluster Name should appear on the AlwaysOn High Availability dialog. MSSQLSERVER will need to be restarted to commit the changes.
Create a Seed or select an existing Database
Create a seed database.
At least one database must exist to create a new Availability Group in Step 9 below. This step is not required when installing SharePoint Server 2010 using DBA created databases. For information on installing SharePoint Server 2010 using DBA created databases see Deploy by using DBA-created databases (SharePoint Server 2010).
Backup the Seed or an existing Database
Backup the Seed Database
Prior to adding a database to an Availability Group a FULL backup of the database must exist.
Create a Network Share
A network share must exist and must be accessible by all nodes in the AlwaysOn configuration in order to perform initial data synchronization.
Create an Availability Group
Create a new Availability Group
The following restrictions exist for using the New Availability Group wizard to start data synchronization:
For each database in the availability group, the Start Data Synchronization page displays the progress of the following operations:
Displays the name of the server instance that will host the availability replica.
Read Mode in Secondary Role
Specifies whether the availability databases on this replica location will be readable when the availability replica is serving as a secondary replica (performing the secondary role).
Select one of the following values from the drop-down list:
Disallow ConnectionsNo direct connections are allowed to secondary databases of this replica. They are not available for read access.
Allow Only Read Intent ConnectionsOnly direct read-only connections are allowed to secondary databases of this replica. The secondary database(s) are all available for read access.
Allow All ConnectionsAll connections are allowed to secondary databases of this replica, but only for read access. The secondary database(s) are all available for read access.
Indicates the role that the new replica will initially perform: Primary or Secondary.
Create a Client Access Point
An access point is a name and associated IP address information. For additional information on Client Access Points in a Failover Cluster see also Understanding Access Points (Names and IP Addresses) in a Failover. The Client Access Point will be used when configuring SharePoint 2010.
Configure SharePoint Server 2010
Start the SharePoint 2010 Products Configuration Wizard.
Create a new server farm specifying the name of the Client Access Point as the name of the database sever.
Add Databases to the Availability Group
Once all databases have been added to one or more Availability Groups the configuration is complete.
I am a bit confused, you state that SP 2010 is not supported on Denali although the 2010 SP1 whitepaper (go.microsoft.com/fwlink) states:
Installing on SQL Server Code Name “Denali”
SP1 provides support for running SharePoint 2010 with SQL Server Code Name “Denali” in addition to providing ongoing support for SQL Server 2008 and SQL Server 2005.
Now it would be bad to use Denali for your farm as you cannot upgrade from CTP to
RTM but the 2 statements seem to contradict each other.
In Service Pack 1 we added support for SQL Server Code Name "Denali" which included support for installing on this database server. The changes in Service Pack 1 were designed to support some deprecated types in this version of SQL Server; however, we don't support deploying on SQL Server Code Name "Denali" in production environments at this time. In brief, SharePoint 2010 cannot be installed on SQL Server Code Name "Denali" without having Service Pack 1 installed. If Service Pack 1 is not installed, PSConfig will fail when attempting to create a new Configuration Database.