Skip to main content

We run into problems with our rapport_queue. Problem is that we have more than 1 process adding rows into the table. Sometimes there is a conflict. We think a unique id could help, so a key with seed. Is that possible, why is that not done?

Hi eurban, 

I assume this is about the reporting service? 

You can set up the underlying data model as you wish, as long as the required stored procedures return the correct data. More info can be found here

Just update the `rapport_queue` table to use an identity field and you shouldn’t have any concurrency problems anymore.


Thanks Jasper


Reply