Difference between revisions of "SQWareProduction:general"
Expdbtools (talk | contribs) (→utilisation) |
Expdbtools (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | == | + | == Presentation == |
| − | === | + | === Usage === |
| − | + | It's the module locally operating of RDBMS. It is entirely written in ksh and sql. <br> | |
| − | + | It allows to manage the operation for RDBMS.<br> | |
<br> | <br> | ||
| − | + | Example uses of the tool: | |
| − | * | + | *Backup |
| − | * | + | *Recovery |
| − | * | + | *Compute statistics |
| − | * | + | *Indicators collection to store in referential database [[SQWareRepository:general|SQWareRepository]]® |
| − | * | + | *Rotate logs |
*.... | *.... | ||
<br> | <br> | ||
| − | + | 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®!<br> | ||
| − | + | Links to different plugins of the module SQWareProduction® : | |
| − | *[[SQWareProduction:oracle| | + | *[[SQWareProduction:oracle|Plugin Oracle]] |
| − | *[[SQWareProduction:sybase| | + | *[[SQWareProduction:sybase|Plugin Sybase]] |
| − | *[[SQWareProduction:mysql| | + | *[[SQWareProduction:mysql|Plugin Mysql]] |
| − | *[[SQWareProduction:mssql| | + | *[[SQWareProduction:mssql|Plugin Mssql]] |
| + | *[[SQWareProduction:ingres|Plugin Ingres]] | ||
<br> | <br> | ||
| − | [[Downloads| | + | [[Downloads|Download the latest stable versions]]<br> |
| − | === | + | === Explanation of directories === |
| − | + | Directories located in $gvsqw_<RdbmsTrigram>Bin (RdbmsTrigram=Ora,Syb,Mys,Msq,Ing): | |
| − | *bin : | + | *bin : Directory containing standard scripts |
| − | *bin_cust : | + | *bin_cust : Directory containing customs scripts for your environnement |
| − | *etc : | + | *etc : Directory containing the standard files of configuration |
| − | *etc_cust : | + | *etc_cust : Directory containing the customs files of configuration for your environnement (overload standards) |
| − | *lib : | + | *help : Directory containing the standard files of help |
| − | *lib_cust : | + | *help_cust : Directory containing the customs files of help for your environnement |
| − | *spm : | + | *lib : Directory containing the generic shell function librairies |
| − | *tools : | + | *lib_cust : Directory containing the generic shell function librairies (overload standards) |
| − | *tools_cust : | + | *spm : Contain sql query toolkit |
| − | *menu : | + | *tools : Directory containing the standard scripts used on an ad hoc |
| − | *menu_cust : | + | *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 | ||
{{Warning_custom}} | {{Warning_custom}} | ||
| − | == convention | + | == Naming convention of files == |
| − | + | The majority of files are named with prefixes: | |
| − | * sqwora_* : | + | * sqwora_* : for Oracle |
| − | * sqwsyb_* : | + | * sqwsyb_* : for Sybase |
| − | * sqwmys_* : | + | * sqwmys_* : for Mysql |
| − | * sqwmsq_* : | + | * sqwmsq_* : for Mssql |
| − | + | <br> | |
| − | * *.ksh : | + | The majority of files are named with suffixes: |
| − | * *.cfg : | + | * *.ksh : for scripts |
| − | * *.lib : | + | * *.cfg : for configuration files |
| + | * *.lib : for function librairies | ||
{{Warning_custom}} | {{Warning_custom}} | ||
<br> | <br> | ||
| − | == convention | + | == naming convention in scripts == |
{{ExpNomVars}} | {{ExpNomVars}} | ||
Revision as of 23:26, 14 December 2010
Contents
Presentation
Usage
It's 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
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
Naming convention of files
The majority of files are named with prefixes:
- sqwora_* : for Oracle
- sqwsyb_* : for Sybase
- sqwmys_* : for Mysql
- sqwmsq_* : for Mssql
The majority of files are named with suffixes:
- *.ksh : for scripts
- *.cfg : for configuration files
- *.lib : for function librairies
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
