Table lock issues during upgrade from 2009 -> 2013

AronChan

Hi All

Im currently attempting to upgrade a database from 2009R2 to 2017.

On the step where i upgrade the database from 2009 to 2013 by opening it in the development invironment im experiencing issues with table locks.
(this is the step where sql data types and colation is changed)

I have tried running the database in single user and multi user.

I have tried turning off all service tiers and taking all other databases offline. There are no maintenance or other sql jobs interfering with the upgrade.

Below i have attached some screenshots showing the problem.





I have redacted the database and table names in the screenshots above due to my customers privacy.

However i think you get the idea.

Any ideas would be greatly appreciated - See you all at TechDays

Slawek_Guzek

Hi,

The 3rd screenshot says that your database is monitored by the SQL's Change Data Capture feature. I guess that CDC maintains its own connection, or just keeps a share lock on the database, which prevents the database to be switched into single-user mode for conversion.

Slawek

Slawek_Guzek

Hi,

The 3rd screenshot says that your database is monitored by the SQL's Change Data Capture feature. I guess that CDC maintains its own connection, or just keeps a share lock on the database, which prevents the database to be switched into single-user mode for conversion.

Slawek

AronChan

Thank you Slawek. It was indeed the CDC messing with me.