How to Verify if Skype for Business Server 2015 Database Updates Completed Successfully


Update 5/17/17 - Added database versions for May 2017 Cumulative Update.
Update 2/13/17 - Added database versions for February 2017 Cumulative Update.
Update 11/4/16 - Added database versions for November 2016 Cumulative Update.
Update 6/27/16 - Added database versions for June 2016 Cumulative Update.
Update 3/18/16 - Added database versions for March 2016 Cumulative Update.
Update 11/17/15 - Added database versions for November 2015 Cumulative Update.
Update 10/1/15 - Added database versions for September 2015 Cumulative Update.
Update 6/19/15 - Added database versions for June 2015 Cumulative Update.

You can find the Lync Server 2013 database versions here.

After downloading and installing Skype for Business Server 2015 updates from KB3061064, it is important to remember to go back and apply the back end database updates.  After applying the back end database updates, you can use the Test-CsDatabase cmdlet to make sure that the databases are up-to-date.

The cmdlet will show you the expected version and the installed version, as well as whether or not the database is up-to-date:

 

The tables below list the back end database versions for RTM as well as each cumulative update:

Cumulative Update Back End Databases
rtcxds  rtcshared  rtcab rgsconfig  rgsdyn  cpsdyn  LcsLog LcsCDR  QoEMetrics  xds lis
RTM 15.13.9 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.8 10.15.4 3.1.1
June 2015 15.13.9 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.8 10.15.4 3.1.1
September 2015 15.13.9 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.8 10.15.4 3.1.1
November 2015 15.13.9 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.9 10.15.4 3.1.1
March 2016 15.13.10 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.9 10.15.4 3.1.1
June 2016 15.13.10 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.9 10.15.4 3.1.1
November 2016 15.13.10 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.12 10.15.4 3.1.1
February 2017 15.13.10 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.12 10.15.4 3.1.1
May 2017 15.13.11 5.0.1 62.42.12 5.5.1 2.2.1 1.1.2 24.40.2 39.85.10 62.93.12 10.15.4 3.1.1

 

Cumulative Update Back End Databases
mgc mgccomp
RTM 1.42.1 1.7.0
June 2015 1.42.1 1.7.0
September 2015 1.42.1 1.7.0
November 2015 1.42.1 1.7.0
March 2016 1.42.1 1.7.0
June 2016 1.42.1 1.7.0
November 2016 1.42.1 1.7.0
February 2017 1.42.1 1.7.0
May 2017 1.42.1 1.7.0

 
 ky

Comments (8)

  1. Anonymous says:

    Update 5/1/15 - Added database versions for May 2015 Cumulative Update. Update 2/19/15 - Added database

  2. Tobie Fysh says:

    Correct me if I'm wrong but there doesn't seem to be a difference in any of the version numbers between RTM and June 2015 in the above tables.

    Is that because there:
    -- are no changes (and as such there is no need to run the back end database updates)
    or
    -- are changes but the versioning in the DB was not moved on (so we do need to run the back end database updates but wont be able to tell if they are successful)?

  3. dodeitte says:

    @Tobie Fysh

    There weren't any changes to the database schema between RTM and the June 2015 CU. You don't need to run the back-end database updates, although it won't affect anything if you do.

    1. Richard says:

      I'm not sure that's true. The instructions for CU's specifically give instructions to install-csdatabase -update even if the DB version number hasn't changed. Additionally there were changes to sprocs that would have required some modifications. I was confused on these points as well as the test-csdatabase provides the same version number, so I opened a case with Microsoft. They state that there are changes, even though the database version number hasn't changed. Who to believe??

      1. @Richard: "They state that there are changes, even though the database version number hasn’t changed."

        Thats what I call typical Microsoft... no comment. Good luck for any Sfb engineer out there to figure out if INSERT-ANY-RANDOM-CUSTOMER-NAME-HERE backend database has OR hasnt been updated.

  4. Pat Richard says:

    Database versions don't change with the Oct 2015 update, either.

  5. Tobie Fysh says:

    Can we have the above updated for the Feb CU please (looks like its all the same as November :-))

Skip to main content