ProClarity Dashboard Server Migration to a New Database Server


What would you do if you needed to change your ProClarity Dashboard Server database instance name?  Microsoft BI product installations have a separate data tier option.  In other words, the database can be on a different machine than the actual product (like ProClarity).  Occasionally, you may have a need to change your database server or move your data to a new database instance on the same machine.  Maybe you have outgrown your current hardware and need a larger SQL Server machine.  In any case, you are going to have to backup and restore the database, ensure that you have the correct logins and permissions, and change any application configurations to use the new database instance.  Let’s look into these items and see how to make the changes for ProClarity Dashboard Server.

Preparing the Database Machine

There is only one database for ProClarity Dashboard Server. I posted previously about Database Migrations – Configure Logins and Permissions.  This post gives you information about:Backup and Restoration of the SQL Database (Data contained in each database).

After you complete the work above, your new database machine is ready and the data and access to the configuration data is ready.

 

Configure the ProClarity Dashboard Server

Step 1. Make a copy of the data.config file.

Find the ProClarity Dashboard Server data.config file.  It is located in the ProClarity Dashboard folder.  By default, it is located here:

C:\program files\proclarity\proclarity dashboard server\config

Change directory by executing the following command:

cd C:\program files\proclarity\proclarity dashboard server\config

Path

Copy the data.config file and rename the copy to data.config.original.  The data.config.original file is a backup of this file should we need to restore it.The original file (and it’s copy) will look something like this:

<snip>

<connectionStrings configProtectionProvider=”DataProtectionConfigurationProvider”>
<EncryptedData>
<CipherData>
<CipherValue>ExampleReallyLongCipherValueStringThatIsShortenedAndReadable</CipherValue>
</CipherData>
</EncryptedData>
</connectionStrings>

</snip>

Step 2. Unencrypt the data.config file

Change directory by executing the following command:

cd C:\program files\proclarity\proclarity dashboard server

Run this command to unencrypt the data.config file:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis –pd “connectionStrings” -app “/Dashboard”

Your data.config file will now look something like this:

<snip>

<connectionStrings>
<add name=”Default” connectionString=”server=OldServerDB;database=ProClarity_DashboardServer;User ID=passqladmindashboard;Password=P4ssw0rd”
providerName=”System.Data.SqlClient” />
<add name=”AesEncryptionKey” connectionString=”CAa4WSnHT1uq6EMMnjl6xOuenv9mmS0AWrxMWXhHVQY=” />
</connectionStrings>

</snip>

Step 3. Change the database name

Remember that the data.config file is in the config directory.

Change the database name from OldServerDB to NewServerDB

Your data.config file will now look something like this:

<snip>

<connectionStrings>
<add name=”Default” connectionString=”server=NewServerDB;database=ProClarity_DashboardServer;User ID=passqladmindashboard;Password=P4ssw0rd”
providerName=”System.Data.SqlClient” />
<add name=”AesEncryptionKey” connectionString=”CAa4WSnHT1uq6EMInjl6xOuenv9mmS0AWrxMWXhHVQY=” />
</connectionStrings>

</snip>

Step 4. Encrypt the file

Make sure you are in the “C:\program files\proclarity\proclarity dashboard server” before you execute this command.  Run this command to encrypt this file

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -pe “connectionStrings” -app “/Dashboard” -prov “DataProtectionConfigurationProvider”

Your data.config file will be encrypted again with a new <CipherValue>

The connection information in the data.config file should now be encrypted and look something like the data.config.original file with different encrypted values.

Step 5. Reboot the server

Restart the ProClarity Dashboard Server and reboot the server to insure that the application can connect to the database on the new server.

If there was an issue, you can restore the original file by deleting the current data.config file and renaming the data.original.config file to data.config and rebooting the server once again.

Notes:

For more information on how to encrypt and decrypt the config file, see: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/paght000005.asp

If you try to copy and paste the commands from this post, sometimes the “minus” sign and “dash” symbol get superimposed.  It is best to type the command instead of using cut and paste.

FUTURESULTS, LLC Blog and FUTURESULTS, LLC Web Site are both created by Robert Lambrecht.

del.icio.us Tags: , , , , ,
Advertisements
This entry was posted in Microsoft BI, ProClarity and tagged , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s