Activities of "leonkosak"

We will definitely run SQL profiler, but we suspect that this issue is not SQL related. We saw this problem in two different environments (different customers and development environments). Even 2MB file is a poblem (multiple seconds execution time in AbpAuditLogs).

Basically, my stupidity. We moved the current database from a local environment to Azure and then created a new tenant with the connection string to this database. But the tenant id was different from the value in the new host environment.

Correct steps:

• Create a blank new database in a new environment
• Create a new tenant in a new environment with a connection string to this blank database
• Restore existing tenant database to the new environment
• In all tables with TenantId column in a database, update value to new tenant id value

Of course, the version of an application (and database) has to be the same during migration.