DB check on startup fails if the tables are there, but empty

Hello,
We were migrating a database containing the Hangfire schema.
The migration script failed, so the hangfire schema was there, but without the seed data.
As a result, when the app pool was starting up Hangfire tried to create the tables again even though they were there already, so the script was failing and the pool startup would crash out. We fixed it by copying the seed data into the tables.

Cheers,
Steven

The issue does not name specific files or tests. Start by reproducing Hangfire startup with the schema tables present but without seed data, then trace the schema-initialization path; done means startup no longer attempts a failing recreation when the tables already exist.

Written by the indexing model from the issue text.