Standards to create the constraints
Rule
Each table must have one or more unique identifiers. At least one must be implemented as a primary key.
The unique identifier must have true business meaning where possible, and not simply be a generated sequence number. A surrogate key may be used where performance considerations would warrant it.
If relationships exist [...]
General Naming Conventions
Names must be a maximum of 30 characters long.
Unless absolutely necessary only alphanumeric characters and underscores should be used.
Each word in a name must be separated by an underscore.
Names are not to be considered case-sensitive.
A name cannot be a Sybase SQL Server Reserved Word or Keyword. (Please refer to the Sybase Adaptive Server [...]
No.
Item
1
Standards/documentation
Database objects names less than or equal to 30 characters
Stored procedures P<event type>_< procedure_name >.
Event Type:
P – Process, S – Select, I – Insert, U – Update, D – Delete, IU – Insert/Update
Conformance to coding standards
Naming conventions to be followed for database objects such as tables,indexes,views,constraints,triggers.
Documentation in code:
Sufficient
Redundant
Correct (conforms to code)
2
Logic coverage
Programming logic:
correct (conforms to [...]
A default installation of Sybase ASE has a small tempdb located on the master device. Almost all ASE implementations need a much larger temporary database to handle sorts and worktables and therefore DBA’s need to increase tempdb.
This document gives some recommendations how this could be done and describes various techniques to guarantee maximum availability of [...]
