Using the <Database> tab in the Validation Rules dialog, you can specify the validation expression for your target server. You click Validation Rules on the Model menu, then click the <Database> tab.
Note: For information on validation rules when Oracle is your DBMS, see Oracle Validation Rules.
The <Database> tab includes the following fields, buttons, and check boxes:
Opens the New Validation Rule dialog in which you can enter the name of a validation rule. In a logical/physical model, the physical validation rule name defaults to the logical validation rule name that you specify.
Opens the Rename Validation Rule dialog in which you can edit the name of the selected validation rule.
Deletes the selected validation rule.
Lets you enter an expression in the correct syntax for the selected server to create a server-side validation expression.
Indicates that the new rule is to apply to the server when you select this check box.
The following options are specific to individual target servers, and affect how a constraint is implemented in the schema:
Defines the message that appears if a user attempts to enter an invalid value.
Lets you enter the message you want to display if a user attempts to enter an invalid value.
Implements table-level or column-level validation rules as FIELDPROC clauses in CREATE TABLE statements in the generated schema.
Implements table-level or column-level validation rules or both as INTEGRITY clauses in CREATE TABLE statements in the generated schema.
Implements column-level or table-level validation rules or both as sp_bindrule clauses in CREATE TABLE statements in the generated schema.
Implements table-level or column-level validation rules or both as CHECK clauses in CREATE TABLE statements in the generated schema.
Counts the number of times that a constraint name is used. A number is appended to the constraint name each time it is used to make the constraint name unique. You can enter a number with which to begin the count in the Unique Naming Count box. Check your database documentation for the maximum number of times that a unique constraint name can be used.
Resets all the validation rules' unique constraint naming counts back to zero.
NOT FOR REPLICATION in ALTER TABLE or CREATE TABLE statements disables foreign key constraint checks on data inserted by distribution during replication. Disabling constraints can improve performance and streamline replication processes. For example, when rebuilding or replicating databases at a remote site there is no need to repeat constraint checks because the integrity of the data was checked when it was entered into the original database.
| Copyright © 2009 CA. All rights reserved. | Email CA about this topic |