When you perform administrative tasks on a database, you should not run certain processes concurrently. In other cases, running certain processes concurrently might also affect performance. The table below shows a matrix of these different processes:
Process 2 |
Make Model Changes |
Bulkload |
Backup |
Report or Drawing Extraction |
|||
Process 1 |
Bulkload |
Sync model with Catalog |
Project Management Backup |
SQL Backup |
|||
Bulkload |
Bulkload |
Risk |
- |
No |
No |
No |
Risk |
Synchronize Model with Catalog |
Risk |
No |
- |
No |
No |
Yes |
|
Regenerate Report DB |
Risk |
No |
No |
Slow |
Slow |
No |
|
DB Maintenance |
Database Integrity |
Slow |
Yes |
Slow |
Yes |
Yes |
Slow |
Clean DB Command |
Risk |
Yes |
Yes |
Yes |
Yes |
Yes |
|
DB Maintenance |
No |
No |
No |
No |
No |
No |
|
Check Fragmentation |
Yes |
Yes |
Yes |
No |
No |
Yes |
|
Backup |
Project Management Backup |
Yes |
No |
No |
- |
Slow |
Yes |
SQL Backup |
Yes |
No |
No |
Slow |
- |
Yes |
|
Report & Drawing |
Report Extraction |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Drawing Extraction |
Yes |
Risk |
Yes |
Yes |
Yes |
Yes |
|
SPR |
SPR Data Creation |
Slow |
Slow |
No |
Yes |
Yes |
Yes |
IFC |
IFC |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Attach/Detach R3D Models |
Attach/Detach R3D Models |
Slow |
Slow |
Slow |
Slow |
Slow |
Slow |
Legend
-
Yes - Processes can be run concurrently with no risks or performance impact.
-
No - Processes cannot be run concurrently.
-
Risk - Processes can be run concurrently, but there are risks involved.
-
Slow - Processes can be run concurrently. However, you will see slower performance while the processes are running.
Smart 3D Rule Checker Service
When some database intensive tasks are in progress, the Rule Checker service needs to be stopped. Follow the guidelines provided in the table.
Can Rule Checker run? |
Comment |
||
Bulkload |
Bulkload |
Yes |
Recommend stopping the service if Bulkload involves:
|
Synchronize Model with Catalog |
No |
Stop the service until the Synchronize process finishes. |
|
Regenerate Report DB |
No |
Filters in the model depend on the Reports database views. As such, filters can fail if the Reports database is being regenerated. |
|
DB Maintenance |
Database Integrity |
Yes |
|
Clean DB Command |
Yes |
Recommend stopping the service. The Clean DB command can delete objects, potentially causing concurrency issues while Rules are trying to access/modify an object.. |
|
DB Maintenance |
No |
Strongly recommend stopping the service. |
|
Check Fragmentation |
Yes |
Strongly recommend stopping the service as running it can slow down the SQL Server resources available to the RuleChecker process. |
|
Backup / Retrieve |
Logical Backup |
Yes |
Recommend stopping the service to produce a meaningful backup. |
SQL Backup |
Yes |
Recommend stopping the service to produce a meaningful backup. |
|
Plant Retrieval (Overwrite) |
No |
Restart the service from the beginning. |
|
Selective Recovery of Objects |
Yes |
Recommend stopping the service. This command can delete/paste objects, potentially causing concurrency issues while Rules are trying to access/modify an object. |
|
Report & Drawing |
Report Extraction |
Yes |
|
Drawing Extraction |
Yes |
||
SPR |
SPR Data Creation |
Yes |
|
IFC |
IFC |
Yes |
|
Modeling |
Modeling |
Yes |
Depending on the Rules logic, such as whether objects are being updated, it is possible to end up in a concurrency situation. We strongly recommend increasing the delay time. Note that an increased delay time only reduces the chances of concurrency issues but does not completely eliminate them. When a concurrency error happens, one of the transactions will be aborted. Should this happen to the RuleChecker's Rule's transaction, you will need to scan the log files for the objects included in that transaction and then modify them to bring them back into the queue of objects processed by RuleChecker. |