OLTP & C/S Structured Design

mysql Installation Upgrading running Stopping MySQLAdmin Users and Privileges Create Tables Alter Tables String or Text Numeric Function Date & Time Date & Time Format Grouping Join Statement Grant & Revoke Stored Procedure OLTP & CS Structure Select Statement

OLTP & C/S Structured Design

OLTP - stands for On-Line Transaction Processing and a summary of it's nature are listed below.

C/S - stands for Client / Server processing and a summary of it's nature is also listed below.

OLTP

Topic	Issues
Locking	Persistent type, either Record or File locking in nature, and there are cases where You have to locally perform the lock / unlock process
Network Traffic	Heavy to very Heavy in nature, required min. transfer rate would be 10 mps(LAN) full- duplex, ideal would be 100 mps full-duplex
Auto_increment	This SQL features which automatically increment any numeric field in a table will be executed with out delay, and the Field option of NOT NULL will be effective
Validation	executed at once, with out delay directly from the Host SQL engine, but uses both Host and Local resources at once
Commit	every time any Update, Insert, Delete, Select operations

Client / Server

Issues	Hint & Comments
Locking	Done at SQL Server end, optimistic support multi-locks on any record in a table, unless altered by code Normally, the SQL Server Engine performs the proper safety parameters for any Transaction(s) in this Client / Server environment
Network Traffic	Low, due to the nature of Client / Server environment. Normally, the Client sends a request to the SQL Server and it would return a result set back to the requesting Client. In Other words, the Client only have a very limited amount of data based on what was requested and what was found, Hence reduces the pockets send and received at one time via local network or related data highway
AUTO_Increment	DO Not include the "NOT Null" field property when declaring any field that would require Auto_Increment feature After an Insert operation, Auto_increment is not Invoke due to the reason that You are working with a Local copy of the actual result, set send back from the SQL Server earlier
Validation	Delayed from the Server End and it would be much better, If done on a local basis If Stored Procedure and Triggers are supported by your SQL Engine, then it would be an advantage to use them so For Triggers, use the Before Insert option For Stored Procedure, use this to process and validate
COMMIT	for every Select, Update, Insert, Delete operation, the current changes made are stored locally in the Client Data Set's Delta
Error Handling	C/S operation requires a Client Data Set to handle the local side for the Client use the ReconcileError Dialog that comes with Borland