How to Migrate Citrix Database from SQL Express Server to SQL Server 2019 Part 1

 How to Migrate Citrix Database from SQL Express Server to SQL Server 2019 Part 1

Summary

I wanted to go through migrating from a SQL Express database to a Standard SQL Server from a CVAD perspective. When I set up my lab, I installed the SQL Express portion( On purpose). I set it up on SQL Express as I wanted to see the painful Delivery Controller experience and to give me a chance to perform this operation. Citrix has documented this, and in this blog post, I will take you through moving it from a SQL Express instance to a SQL Single Instance. I understand this is not a typical setup, which is why I chose this setup back then. In Part 2 of the blog post(to come), I will share how to move the New SQL Single Instance into a SQL AG Setup. It will allow me to document and share the steps with the community for those running natively on-premises. It will clarify how to move a SQL DB to another server. 

The links I will be following are below

• https://support.citrix.com/article/CTX318273/how-to-migrate-citrix-database-on-sql-express-to-full-microsoft-sql-server

• Migrate Citrix databases to new database SQL server (cluster, Always On or Mirroring)

• Update database connection strings when using SQL Server high availability solutions (citrix.com)

1. Install SQL Express Management Studio on Delivery Controller where you have your Citrix Database Installed using the link below:

1. Download SQL Server Management Studio (SSMS) - SQL Server Management Studio (SSMS) | Microsoft Learn

2. Take snapshots of the Delivery Controllers and Citrix Database Full Backups before making changes.  In my case, it’s DDC01 and DDC02

1. Snapshots completed

3. Disable Logging to avoid issues on changing connection string for logging connection.

4. When you null out the connection later in this blog and set the new connection. You will get errors if this part is not completed first

1. https://support.citrix.com/article/CTX139447

2. Open Powershell and run:

• Set-logsite -state Disabled

5. At this point, change the DB recovering Model to “Full” on all three databases if not already set.

6. Now we need to back up each Database.

7. I tend to put it on a share that the source and destination SQL servers will be able to access.

1. Please,  follow your change requirements within your organization.

1. CitrixLABLogging

2. CitrixLABMonitoring

3. CitrixLABSite

8. Restore the Databases

1. Now we need to remote into the new SQL Server and Restore the Databases.

2. In this case, it’s LABSQL02. Do this for each Database independently. 

3. Restoring the databases

4. Now repeat the process for Logging and Monitoring the Database. The three Databases have been successful to the destination SQL Server.

9. Enable DDC logins on SQL

1. Now we need to enable the SQL Login for the Delivery Controllers.

10. Map the SQL Logins for each delivery controller to the correct Database with permission. Do this for each one. It is a must to do this for each Delivery Controller.

1. create login [lab\DDC01$] from windows

2. create login [lab\DDC02$] from windows

11. Once you complete step 10, You will need to set the permissions on each Database. I went and checked the roles on the Express DB first and made notes on what each one needed.

1. Database Access and Permission Model for XenDesktop (citrix.com)

12. Logging DB

13. Monitoring DB

14. Site

15. NULL out the DB connection strings on both(all) DDCs

1. Now we need to log on to our Delivery controllers and NULL out the DB connection strings. Run the commands below. Do this on both Delivery Controllers. In my case, its DDC01 and DDC02

## Clear the current Delivery Controller database connections

## Note: AdminDBConnection must be the last command

Set-ConfigDBConnection -DBConnection $null

Set-AppLibDBConnection -DBConnection $null    #7.8 and newer

Set-OrchDBConnection -DBConnection $null      #7.11 and newer

Set-TrustDBConnection -DBConnection $null     #7.11 and newer

Set-AcctDBConnection -DBConnection $null

Set-AnalyticsDBConnection -DBConnection $null # 7.6 and newer

Set-HypDBConnection -DBConnection $null

Set-ProvDBConnection -DBConnection $null

Set-BrokerDBConnection -DBConnection $null

Set-EnvTestDBConnection -DBConnection $null

Set-SfDBConnection -DBConnection $null

Set-MonitorDBConnection -DataStore Monitor -DBConnection $null   #Monitoring Database

Set-MonitorDBConnection -DBConnection $null                      #Site Database

Set-LogDBConnection -DataStore Logging -DBConnection $null       #Logging Database

Set-LogDBConnection -DBConnection $null                          #Site Database

Set-AdminDBConnection -DBConnection $null -force

Example

2. To check, run this.

• get-command get-*DBConnection | select-object -property name | ForEach-Object { $_.name; invoke-expression $_.Name } | fl

16. Set the new Database Strings

1. Note MultiSubnetFailover=True  (is only needed for SQL DAG)

$ServerName = "LABSQL02"

$SiteDBName = "CitrixLABSite"

$LogDBName = "CitrixLABLogging”

$MonitorDBName = "CitrixLABMonitoring"

$csSite = "Server=$ServerName;Initial Catalog=$SiteDBName;Integrated Security=True;MultiSubnetFailover=True"

$csLogging = "Server=$ServerName;Initial Catalog=$LogDBName;Integrated Security=True;MultiSubnetFailover=True"

$csMonitoring = "Server=$ServerName;Initial Catalog=$MonitorDBName;Integrated Security=True;MultiSubnetFailover=True"

 

Set-AdminDBConnection -DBConnection $csSite

Set-ConfigDBConnection -DBConnection $csSite

Set-AcctDBConnection -DBConnection $csSite

Set-AnalyticsDBConnection -DBConnection $csSite # 7.6 and newer

Set-HypDBConnection -DBConnection $csSite 

Set-ProvDBConnection -DBConnection $csSite

Set-AppLibDBConnection –DBConnection $csSite # 7.8 and newer

Set-OrchDBConnection –DBConnection $csSite # 7.11 and newer

Set-TrustDBConnection –DBConnection $csSite # 7.11 and newer

Set-BrokerDBConnection -DBConnection $csSite

Set-EnvTestDBConnection -DBConnection $csSite

Set-SfDBConnection -DBConnection $csSite

Set-LogDBConnection -DBConnection $csSite

Set-LogDBConnection -DataStore Logging -DBConnection $null

Set-LogDBConnection -DBConnection $null

Set-LogDBConnection -DBConnection $csSite

Set-LogDBConnection -DataStore Logging -DBConnection $csLogging

Set-MonitorDBConnection -DBConnection $csSite

Set-MonitorDBConnection -DataStore Monitor -DBConnection $null

Set-MonitorDBConnection -DBConnection $null

Set-MonitorDBConnection -DBConnection $csSite

Set-MonitorDBConnection -DataStore Monitor -DBConnection $csMonitoring

1. Double-check with this command.

• get-command get-*DBConnection | select-object -property name | ForEach-Object { $_.name; invoke-expression $_.Name } | fl

2. Double Check Services

• Get-Command *servicestatus | Select-object -property name | foreach-object { $_.Name; invoke-expression $_.Name | Select-object -property servicestatus} | FL

Note: there are more services than in the screenshot. Here is an example.

17. Now open Citri studio to verify the SQL connection.

18. Run some tests in Citrix Studio to make sure things look ok.

19. Cleanup- (SQL isn’t my expertise)

1. You can clean up the SQL Express data points now that things are on a native SQL server.

2. You still have the Full backups you created, if needed. Although if restored, the data may be off, and you are returning to an express database. No really ideal.

3. Detach the SQL Express Database

4. Wait some time, and remove them.

And there you have it. It seems easy enough, right? Many probably have done this and have scripts and all sorts of tricks. But for those who are not sure. The goal here was to share it and help those in need.