Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
I have a stored procedure (called from Appian’s Execute Stored Procedure smart service) that reads from a view and then creates, updates, or deletes rows in a materialized table that is also sourced from that same view.
The view is heavily used by multiple applications, so I created the stored procedure smart service to read the updated values from the view and reflect them in the materialized table. This process is triggered by various create or update forms across different applications.
Most of the time the stored procedure works, but sometimes it fails with the following error:
Deadlock found when trying to get lock; try restarting transaction
How can I reduce or avoid these deadlocks?
Discussion posts and replies are publicly visible
I do not understand why you directly modify data in that materialized view. Isn't the idea that it updates itself?
Is it not possible to use the Data Fabric for your purposes? The Data Fabric is, effectively, a materialized layer on top of your database. It has a small learning curve, and older applications need to be refactored into it, but it serves its purpose extremely well.