Publishing to a Production Database
The information in this article applies to product: e-Work 5.x 6.x
Discussion
- It is not recommended that an e-Work procedure be published to a database that is experiencing heavy user activity. When a procedure is published, tables are locked and unlocked for the entire time the Designer is publishing. This can cause contentions within the database if the Engine is trying to execute long-running SQL queries, retrieve data, etc. at the same time the Designer is locking tables while publishing a large procedure.
Tagged:
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 156 General Questions
- 149 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 33 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 10 XM Fax
- Follow Categories
