Naming Stored Procedures
When you use a Microsoft® SQL Server™ database for your repository, the repository engine creates stored procedures for the insertion of rows into the repository SQL tables. This topic describes how these stored procedures are named.
The stored procedure name for a table is generated by prefixing the table name with the string "R_i". Because table names are unique, this naming convention will generate unique stored procedure names. If the length of the table name is greater than MaxIdentifierLength-3, however, the table name generation algorithm fails. For this reason, a user may not supply a table name longer than MaxIdentifierLength-3. Supplying a longer name causes the error EREP_BADNAME.
When the user does not provide a table name for an interface, the engine automatically generates the table name from the interface name. If the interface name, with the leading "I" stripped off, is less than MaxIdentifierLength-4, the interface name will be used as the table name. Otherwise, the interface name is truncated to MaxIdentifierLength-7, and a 4-character number is appended to the name to make it unique, before prefixing "R_i.
The engine uses named arguments to call the stored procedures. A named argument starts with the at sign (@) character and is no longer than MaxIdentifierLength. Therefore, the property names, which are also column names, must be no longer than MaxIdentifierLength-1.
MaxIdentifierLength values are 30 characters for SQL Server version 6.5 and 128 characters for SQL Server version 7.0 and SQL Server 2000.
See Also
Naming Objects, Collections, and Relationships