Difference between revisions of "SQWareProduction:general"

From Wiki_dbSQWare
Jump to: navigation, search
(Presentation)
(General architecture diagram SQWareProduction™ (when the module is locally installed):)
Line 42: Line 42:
 
<br>
 
<br>
  
=== General architecture diagram SQWareProduction™ (when the module is locally installed): ===
+
=== General architecture diagram SQWareProduction™ (when the module is locally installed) ===
 
[[Image:General_SQWareProduction.jpg]]
 
[[Image:General_SQWareProduction.jpg]]
  

Revision as of 16:44, 12 November 2011

Presentation

Usage

SQWareProduction™, also known technically as expdbExp®, is the module locally operating of RDBMS.
It is entirely written in ksh and sql.
It allows to manage the operation for RDBMS.
Example uses of the tool:

  • Backup
  • Recovery
  • Compute statistics
  • Indicators collection to store in referential database SQWareRepository™
  • Rotate logs
  • ....

This module is deployed locally on the machine hosting the authorities to manage, in order to avoid any points of weakness related to an NFS mount or whatever. The deployment is done through a simple command SQWareCentral™ module using inventory located in SQWareRepository™!

Links to different plugins of the module SQWareProduction® :

Download the latest stable versions
Installation guide for SQWareProduction™

Explanation of directories

Directories located in $gvsqw_<RdbmsTrigram>Bin (RdbmsTrigram=Ora,Syb,Mys,Msq,Ing):

  • bin : Directory containing standard scripts
  • bin_cust : Directory containing customs scripts for your environnement
  • etc : Directory containing the standard files of configuration
  • etc_cust : Directory containing the customs files of configuration for your environnement (overload standards)
  • help : Directory containing the standard files of help
  • help_cust : Directory containing the customs files of help for your environnement
  • lib : Directory containing the generic shell function librairies
  • lib_cust : Directory containing the generic shell function librairies (overload standards)
  • spm : Contain sql query toolkit
  • tools : Directory containing the standard scripts used on an ad hoc
  • tools_cust : Directory containing the customs scripts used on an ad hoc for your environnement
  • menu : Directory containing the standard menus
  • menu_cust : Directory containing the custom menus for your environnement
Nuvola apps important.png
Warning:
Do not change the standard scripts and configuration files of dbSQWare.

Use directories *_cust for customizations. This will facilitate version upgrades.


General architecture diagram SQWareProduction™ (when the module is locally installed)

General SQWareProduction.jpg

Naming convention of files

The majority of files are named with prefixes:

  • sqwora_* : for Oracle
  • sqwsyb_* : for Sybase
  • sqwmys_* : for Mysql
  • sqwmsq_* : for Mssql
  • sqwing_* : for Ingres


The majority of files are named with suffixes:

  • *.ksh : for scripts
  • *.cfg : for configuration files
  • *.lib : for function librairies
  • *.hlp : for help files
Nuvola apps important.png
Warning:
Do not change the standard scripts and configuration files of dbSQWare.

Use directories *_cust for customizations. This will facilitate version upgrades.


Naming convention in scripts

In general, the following naming convention is used in all scripts of SQWareProduction:

  • gvsqw_ {} : global variable initialized by the environment and / or generic library
  • lvsqw_ {} : local variable initialized by the script and / or a specific library
  • gfsqw_ {} : function defined by a generic library
  • lfsqw_ {} : function defined by the script and / or a specific library