Darren Liu's Blog

Archive for the ‘SQL’ Category

CRM 2013 Reporting and SQL 2012 AlwaysOn

leave a comment »

Just want to resurface a blog by a colleague from UK on CRM Reporting and SQL 2012 AlwaysOn since I am implementing it with my customer. Adding it to my blog just in case I need to do it again in the future.



Written by darrenliu

05/13/2014 at 8:57 pm

Posted in CRM 2013, Report, SQL

Tagged with , , ,

Installing CRM Using SQL Server DNS Alias

leave a comment »

In most enterprise Dynamics CRM project, the customer would like to install CRM using the SQL server DNS alias instead of the server name. One of the reasons for doing it is because they need to support their Disaster Recovery (DR) strategy. 

CRM does not allow you to use the alias because the Environment Diagnosis Wizard (EDW) did not have the ability to check for a SQL DNS alias, therefore it does not allow you to move to the next step even though it’s supported.

You have two options to solve this problem.

  • Option #1: Install CRM using the actual SQL server name.  After the installation is completed, modify the database connection string in the MSCRM registry and the MSCRM_CONFIG database.
  • Option #2: Add the IgnoreChecks key to the MSCRM ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM]) registry to by pass the EDW check to continue with the installation.  Make sure that you setup the DWORD value to “1”. If you are going with this option, please make sure all of your other checks passed before adding the IgnoreChecks key.

Hope this helps!

Written by darrenliu

04/10/2012 at 1:55 am

Posted in CRM, Installation, SQL

Tagged with , , ,

SQL Server DNS Alias

with 2 comments

The customer wants to setup DNS for SQL Server because it’s part of their Disaster Recover (DR) plan.  I learned something from the folks in our team and Grant G from the PFE team on how to do it. Posting the step here just in case that I need to do it next time.

In order to setup a DNS alias for SQL server/SQL cluster, the first step is make sure DNS alias is in place, SPN is setup correctly.  Once the pre-requisites is setup, following the steps below:

1. Execute the following query.

select @@servername

2. One you’ve verified the server name, execute the following SQL query.

sp_dropserver ‘servername’
sp_addserver ‘aliasname\instancename’,’local

3. After you execute the above query, stop and start the SQL server.

4. Execute the following query again to make sure SQL server is setup correctly.

select @@servername

The steps above assumes that SQL is listening to the default port of 1433.  To configure SQL listen on different port. Please see the following article on MSDN.

How to: Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)

Written by darrenliu

04/03/2012 at 2:36 am