Hi @avandervelden,

It is actually not stuck, but this step takes much longer than others. In 2024.3 coming next week of writing this, this process has been optimized significantly.

This step in 2024.2 can take several minutes and is dependent on the amount of roles, granted tables in those roles in combination with the amount of Table variants in your model.

Edit: when cancelling/aborting this job, ensure that the SQL Server process is also stopped. Otherwise the process is running and using Server capacity.

On DEV it took 6 minutes, on TST it ran already for hours!!

And yes, we have a large model etc, but that's why we switched to Thinkwise - this should not be an issue compared to another platform we had before.

Okay, perhaps SQL Server has chosen a bad plan or the indexes and statistics are out of date, which can have massive impact. Could you run tsf_optimize and try again? 

If that also does not help, we may need to look closer into what exactly is causing this performance degradation. Could you create a ticket with a SF backup? If the database is too large, our support team can supply a FileCap link where you can upload the backup.

Thanks. Worked

tsf_optimize took more than an hour, but we can continue