•
|
•
|
For V1 metadata, see Identifier Restrictions by Identifier Type in Advanced Operations Guide for the maximum length of a table name (the length includes “#,” “##,” underscores, and ID)
|
yes3
|
yes4
|
yes3
|
yes4
|
For V2 metadata, see Identifier Restrictions by Identifier Type in Advanced Operations Guide for the maximum length of a table name (the length includes “#,” “##,” underscores, and ID)
|
yes3
|
yes4
|
yes3
|
yes4
|
yes7
|
yes9
|
|||
yes8
|
||||
1SP stands for stored procedure
2The database engine automatically appends the name of the stored procedure and a session-specific ID to the user-defined name to ensure a unique table name. This functionality is transparent to the user.
3The total length of the table name includes “#” or “##”, plus an underscore, plus a session ID. The session ID can be 8, 9, or 10 bytes depending on the operating system. See Identifier Restrictions by Identifier Type in Advanced Operations Guide.
4The total length of the table name includes “#” or “##”, plus an underscore, plus the name of the stored procedure, plus an underscore, plus a session ID. The session ID can be 8, 9, or 10 bytes depending on the operating system. See Identifier Restrictions by Identifier Type in Advanced Operations Guide.
5Constraint returns a warning but table is created.
6A table can be created and populated with data with a single SELECT INTO statement.
7The table name already exists from the first execution of the stored procedure.
8If end of session occurs before the execution of the procedure ends.
|