CMS - MS SQL Server / Sybase Reference Guide
MS SQL Server / Sybase Reference Guide
This document provides some more detailed information about the objects and links that are stored in the Analysis Service. Other technical information may also be available.
Object Types
Objects detected by the analyzer are summarized in the following table:
| Object | Name |
| Instance | |
| Database | |
| Schema | |
| Trigger | |
| Function | |
| Procedure | |
| Table | |
| View | |
| Table Column / View Column | |
| Index, Foreign Key Constraint, Primary Key Constraint, Unique Constraint |
Note that Synonyms are not supported: any reference to a synonym is silently ignored by the analyzer (no message issued).
Link Types
Links created by the analyzer are summarized in the following table:
| Called/Parent (X) → Caller/Child (Y) ↓ | instance | database | schema | table | table column | view | view column | unique constraint | PK | FK | trigger | function | procedure | ←Called/Parent (X) ↓Caller/Child (Y) |
| instance | area (instance) | |||||||||||||
| database | Belong | |||||||||||||
| schema | Belong | container (schema) | ||||||||||||
| table | Belong | Refer Integrity (FK –> PK) | Fire: Before Insert/Update/Delete, After Insert/Update/Delete, For each row Insert/Update/Delete and For all row Insert/Update/Delete | table | ||||||||||
| table column | Belong | Refer Integrity (FK –> PK) | table column | |||||||||||
| index | Belong | Rely on | Rely on*) | index (simple, bitmap, function based) | ||||||||||
| view | Belong | Use (select) | Access (read) | Access (read) | Fire: Instead of Insert/Update/Delete, For each row Insert/Update/Delete and For all row Insert/Update/Delete | view | ||||||||
| view column | Belong | view column | ||||||||||||
| unique constraint | Belong | Rely on | Unique constraint | |||||||||||
| PK | Belong | Rely on*) | PK | |||||||||||
| FK | Belong | Rely on*) | Refer Integrity (FK –> PK) | FK | ||||||||||
| trigger | Belong | Use: Use (Select), Use (Insert), Use (Update), Use (Delete) | Access: Access (read), Access (write) | Access: Access (read), Access (write) | Call | Call | trigger DML | |||||||
| function | Belong | Use: Use (Select), Use (Insert), Use (Update), Use (Delete) | Access: Access (read), Access (write) | Access: Access (read), Access (write) | Call | Call | function | |||||||
| procedure | Belong | Use: Use (Select), Use (Insert), Use (Update), Use (Delete) | Access: Access (read), Access (write) | Access: Access (read), Access (write) | Call | Call | procedure |
Support for Microsoft SQL Server 2008
The following is a list of syntax supported by the T-SQL Analyzer:
- Table-value parameters
- MERGE statement
- Initialization of variables at the same time of its declaration in
- Inserting multiple rows in one statement (Row constructors)
- Compound assignment operators
- Grouping Sets
- CREATE/DROP/ALTER Partition
- New date & time data types
- With regard to User Defined Table Types in Microsoft SQL Server 2008:
- When a User Defined Table Type is analyzed by CAST it will be categorized as both a User Defined Type and a User Defined Table Type and will appear under the “SQL Server UDT” and “SQL Server UDT Table” folders in CAST Enlighten and the Discovery Portal.
- If a standard relation table with an identical name as the User Defined Table Type is also located in the same database, then the table will be saved to the Analysis Service, whereas the User Defined Table Type will not be saved either as a User Defined Type or a User Defined Table Type.
- No links are created between client objects (methods) and User Defined Table Types. However, if the client method calls a procedure which references the User Defined Table Type (i.e. via a DECLARE statement) then the User Defined Table Type will present in the database subset - but there is no direct link from the client method to the User Defined Table Type.
