Archive for 'Sybase' Category
SYBASE ADAPTIVE SERVER ENTERPRISE
Release 12.5 GA and above INDEX: I….. .ASE Overview II…..System Databases and Tables III….Transact SQL IV….Transactions V……Isolation Levels VI…..Locking VII…ASE Supported Platforms VIII..ASE Utilities IX…..Component Integration Services (CIS) X……New Features – ASE 15 XI….ASE Resources XII…SYBASE Data Server & Integration Products For Details of the INDEX refer the next pages w.r .to each INDEX.
III. TRANSACT SQL.
III. TRANSACT SQL . Data types List system objects and attributes Creating a table Altering a table Table creation – Alternatives Indexes Clustered vs. non-clustered indexes Creating constraints Defaults Table partitioning Object permissions Binding Rules Modifying a Column Moving an object Views Stored Procedures Triggers Datatypes:– Note:–Table with contents to be drawn…….. . . . [...]
II. SYSTEM DATABASES AND TABLES.
II. SYSTEM DATABASES AND TABLES. When ASE is installed following databases are installed. * master * model * sybsystemprocs * tempdb Optional databases that can be installed are * sybsecurity * sybsystemdb * dbcc * sybdiag * pubs2 and pubs3 ASE databases: master database:– Controls the operation of ASE and stores the information of user [...]
I. Adaptive Server Enterprise(ASE) Overview.
I. A S E OVERVIEW. ASE Server Memory Model Transaction Processing Backup Procedures Recovery Procedures ASE Logins ASE Groups Security and Account Setup Database Creation Storage Concepts Transact SQL Transact SQL Extensions ASE Server:– ASE server consists of Two processes, data server and backup server. Devices house the databases. Master database contains system and configuration [...]
Sybase Formatting Control Structures Standard
Control Structures IF <expression> THEN Executable_statements ELSE Executable_Statements If executable statements are more than one statement then use BEGIN … END block for grouping the statements. Recommendation: One line space after executable statements Executable statements should be indented atleast by 3 spaces. If the executable statements inside an IF statement clause themselves contain another IF [...]
Other Sybase Standard and Guidelines
Rule Where possible, areas of common processing must be implemented by procedures. Note: Maximize re-use of pre-parsed statements. For triggers of any complexity the detailed logic must be coded in procedures which are invoked from within the trigger body. Object names must not be qualified with the owner name. Note: The statement cannot be run [...]
Sybase Naming Convention Standard
The naming convention for variables and constants is as follows: 1. Program Structure The following should be the templates used in T-SQL source code files. Any T-SQL source file should have a file header of the following format (Header) followed by the body of the procedure. Since SQL server doesn’t support the concept of Packages [...]
Sybase Standard for Stored Procedures and Triggers
Rule for Stored Procedures Procedures should be named PROC_<procedure_name> Rule for Triggers Triggers must be named TR<type>_<table name>_<seq> where <type> is ‘I’, ‘U’ or ‘D’ and <table_name> is truncated to 24 characters. (‘I’ represents Insert; ‘U’ represents Update; and ‘D’ represents a delete).
Sybase Identity Columns Creation Standard
Rule Identity columns should be used for all generated numbers where a gap in the sequence is not significant. i.e surrogate primary keys. If control of a sequence needs to be retained then this should be implemented using a row in a specific table which holds the next available number in the sequence, this should [...]
Sybase Standard For Index and Guideline
Rule Primary and Unique Key constraints are automatically indexed by the database when the constraint is enabled and cannot be indexed separately. Foreign Key columns should only be indexed where they improve performance. Additional non-unique indexes must only be created for specific performance reasons on the basis of demonstrated need. Redundant Indexes must be removed. [...]