Version: 12.0.9-3
Build #: 30310
Build Date: 2012-Nov-24 10:50:49 AM
ALLOW_ROW_LOCKS=OFF and ALLOW_PAGE_LOCKS=OFF should not be the default for a new SQL Server ER Model Constraint
1. Open attached ER Model
2. Expand the table node , so that you see the node constraints
3. Right Click on Constraints tree node and create a new Primary Key constraint.
4. You can see that the contraint is created with (ALLOW_ROW_LOCKS = OFF, ALLOW_PAGE_LOCKS = OFF) which is incorrect. These should follow the same rules as the ADS Visual GUI's.
If you use ADS GUI to create a constraint you can look at the Preview SQL to see the DDL and you will see that the allow_row_locks and allow_page_locks clause are not included, and thus delegating the default to SQL Server.
5. Fix for New Unique Constraint as well.
![]() |
939 B
|
40 KB
|
38 KB
initial values for sql server unique key, primary key and check constraints changed to match ads GUI initial values. code change for version 12 & 13
Issue #8079 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build 12.0.13-1 |
No time estimate |
initial values for sql server unique key, primary key and check constraints changed to match ads GUI initial values. code change for version 12 & 13