Difference between revisions of "dbSQWare:general"
Expdbtools (talk | contribs) |
Expdbtools (talk | contribs) (→Tool structure) |
||
| (27 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == Introduction == | |
| − | + | '''dbSQWare™''' is designed for DBAs to facilitate the daily operation of all databases to which they are responsible for: | |
| − | + | * '''dbSQWare™''' provides a common unified socle for a number of RDBMS of the market: Oracle, Sybase, SQL Server, MySQL, DB2-LUW, PostgreSQL and Ingres. This base can quickly accommodate other types of databases with the flexibility of its design. | |
| − | + | * The product also offers a vision of inventory and capacity planning for those less expert, through a web interface. | |
<br> | <br> | ||
| − | + | '''dbSQWare™''' currently represents several months of design, development and testing. Version v3.1 was released in september 2011 that is mature and stable in production. The product is intended (for his party scripts) to Unix / Linux only because it is essentially written in shell ksh and sql. The web part, for its part, is written in PHP, Ajax and Flash Open.<br> | |
| + | [[Downloads | Download the latest stable versions]]<br> | ||
| + | [[Installation | Installation guide]]<br> | ||
| + | |||
| + | == Overall functionality == | ||
| + | Management repositories of DBMS park (CMDB) in a database. <br> | ||
| + | Current and advanced operations on DBMSs Oracle, Sybase, MSSQL, MySql, DB2-LUW, PostgreSQL and Ingres: | ||
| + | * Backup | ||
| + | * Restorations | ||
| + | * Reorganizations | ||
| + | * Statistics | ||
| + | * ... | ||
| + | Collection of indicators and capacity planning with recovery in a database. Check these indicators (collection, volumes, backups, ...) and send alert mails.<br> | ||
| + | Central management of instances (access, scripts execution and automatic controls, ...).<br> | ||
| + | GUI website for restitution of the indicators in tables and graphs.<br> | ||
| + | |||
| + | == Homogeneity == | ||
| + | In use: | ||
| + | * Use consistent, regardless of the DBMS | ||
| + | * Easy adaptation by configuration files | ||
| + | * Only one version of the tool across the park | ||
| + | * The scripts adapt to the version of the DBMS managed | ||
<br> | <br> | ||
| − | + | In the development and evolution: | |
| − | * | + | * Design consistent for all DBMSs |
| − | * | + | * Normalization of code (names, functions, structures, parsing of arguments, ...) |
| − | + | * Behavior modification by overloading bookstores | |
| − | * | + | * Set of standard libraries can be integrated into custom scripts <br> |
| − | * | ||
| − | |||
<br> | <br> | ||
| − | + | ||
| − | * | + | == Tool structure == |
| − | * | + | |
| − | * | + | '''dbSQWare™''' is composed of four interconnected modules:<br> |
| − | * | + | *[[SQWareProduction:general|SQWareProduction™]] |
| + | *[[SQWareRepository:general|SQWareRepository™]] | ||
| + | *[[SQWareCentral:general|SQWareCentral™]] | ||
| + | *[[SQWareWeb:general|SQWareWeb™]] | ||
<br> | <br> | ||
| − | + | '''[[SQWareProduction:general|SQWareProduction™]]''', is the operating module in local. It allows to manage the operation at large for RDBMS: | |
| − | *[[ | + | * Backup |
| − | + | * Restorations | |
| − | *[[ | + | * Statistics |
| − | + | * Ascents alerts | |
| + | * Encapsulation execution jobs | ||
| + | * Execution of unix commands in parallel | ||
| + | * ... | ||
| + | This module also collects a number of indicators that are inserted on the repository database SQWareRepository™. This module consists of one part per DBMS managed. There is no "core" part, each type of DBMS is independent but the scripts are all written by the same standard of development (argument parsing, online help, send mail on error, recovery indicators in SQWareRepository ™, ...).<br> | ||
| + | <br> | ||
| + | |||
| + | '''[[SQWareRepository:general|SQWareRepository™]]''', is the management module of the repository and indicators database. It allows to manage the repository and the indicators stored in databases (the database depending of the type of DBMS managed). This module consists of one part per DBMS managed. There is no "core" part, each type of DBMS is independent but all plugins have the same type of MCD. <br> | ||
| + | <br> | ||
| + | |||
| + | '''[[SQWareCentral:general|SQWareCentral™]]''', is the central module of the tool. It can manage the whole park from this point: | ||
| + | * Centralized collection of indicators | ||
| + | * Deployment of SQWareProduction™ modules by rsync | ||
| + | * Management of "full-text search" in the repositories | ||
| + | * Easy connection via ssh to different instances of the park ... | ||
| + | * ... | ||
| + | This module is based inter alia on the repository database, SQWareRepository™. It is composed of a "core" part common to all managed RDBMSs and a specific plugin for each DBMS (Oracle, Sybase, SQL Server, MySQL and Ingres).<br> | ||
| + | <br> | ||
| + | |||
| + | '''[[SQWareWeb:general|SQWareWeb™]]''', is the web module for graphic indicators. It works with Apache 2 and is written in PHP 5.2, AJAX and Open-Flash. It allows for the presentation of indicators and capacity planning as: | ||
| + | * Graphics (flash) | ||
| + | * Tables (with sorting and formatting locally on the browser) | ||
| + | * Exports Excel | ||
| + | *... | ||
| + | It is based entirely on data contained in the repository database SQWareRepository ™. Refunds are made in much the same way regardless of the DBMS (the specific near it), which makes it more enjoyable and easier navigation. This module is composed of a "core" part common to all managed RDBMSs (template engine, display graphs, tables, ...) and a specific plugin for each DBMS (Oracle, Sybase, SQL Server, MySQL, DB2-LUW, PostgreSQL and Ingres). <br> | ||
| + | |||
| + | == General architecture diagram dbSQWare™ (when the SQWareProduction™ module is locally installed) == | ||
| + | [[Image:General_dbSQWare.jpg]] | ||
Latest revision as of 20:07, 18 January 2013
Contents
Introduction
dbSQWare™ is designed for DBAs to facilitate the daily operation of all databases to which they are responsible for:
- dbSQWare™ provides a common unified socle for a number of RDBMS of the market: Oracle, Sybase, SQL Server, MySQL, DB2-LUW, PostgreSQL and Ingres. This base can quickly accommodate other types of databases with the flexibility of its design.
- The product also offers a vision of inventory and capacity planning for those less expert, through a web interface.
dbSQWare™ currently represents several months of design, development and testing. Version v3.1 was released in september 2011 that is mature and stable in production. The product is intended (for his party scripts) to Unix / Linux only because it is essentially written in shell ksh and sql. The web part, for its part, is written in PHP, Ajax and Flash Open.
Download the latest stable versions
Installation guide
Overall functionality
Management repositories of DBMS park (CMDB) in a database.
Current and advanced operations on DBMSs Oracle, Sybase, MSSQL, MySql, DB2-LUW, PostgreSQL and Ingres:
- Backup
- Restorations
- Reorganizations
- Statistics
- ...
Collection of indicators and capacity planning with recovery in a database. Check these indicators (collection, volumes, backups, ...) and send alert mails.
Central management of instances (access, scripts execution and automatic controls, ...).
GUI website for restitution of the indicators in tables and graphs.
Homogeneity
In use:
- Use consistent, regardless of the DBMS
- Easy adaptation by configuration files
- Only one version of the tool across the park
- The scripts adapt to the version of the DBMS managed
In the development and evolution:
- Design consistent for all DBMSs
- Normalization of code (names, functions, structures, parsing of arguments, ...)
- Behavior modification by overloading bookstores
- Set of standard libraries can be integrated into custom scripts
Tool structure
dbSQWare™ is composed of four interconnected modules:
SQWareProduction™, is the operating module in local. It allows to manage the operation at large for RDBMS:
- Backup
- Restorations
- Statistics
- Ascents alerts
- Encapsulation execution jobs
- Execution of unix commands in parallel
- ...
This module also collects a number of indicators that are inserted on the repository database SQWareRepository™. This module consists of one part per DBMS managed. There is no "core" part, each type of DBMS is independent but the scripts are all written by the same standard of development (argument parsing, online help, send mail on error, recovery indicators in SQWareRepository ™, ...).
SQWareRepository™, is the management module of the repository and indicators database. It allows to manage the repository and the indicators stored in databases (the database depending of the type of DBMS managed). This module consists of one part per DBMS managed. There is no "core" part, each type of DBMS is independent but all plugins have the same type of MCD.
SQWareCentral™, is the central module of the tool. It can manage the whole park from this point:
- Centralized collection of indicators
- Deployment of SQWareProduction™ modules by rsync
- Management of "full-text search" in the repositories
- Easy connection via ssh to different instances of the park ...
- ...
This module is based inter alia on the repository database, SQWareRepository™. It is composed of a "core" part common to all managed RDBMSs and a specific plugin for each DBMS (Oracle, Sybase, SQL Server, MySQL and Ingres).
SQWareWeb™, is the web module for graphic indicators. It works with Apache 2 and is written in PHP 5.2, AJAX and Open-Flash. It allows for the presentation of indicators and capacity planning as:
- Graphics (flash)
- Tables (with sorting and formatting locally on the browser)
- Exports Excel
- ...
It is based entirely on data contained in the repository database SQWareRepository ™. Refunds are made in much the same way regardless of the DBMS (the specific near it), which makes it more enjoyable and easier navigation. This module is composed of a "core" part common to all managed RDBMSs (template engine, display graphs, tables, ...) and a specific plugin for each DBMS (Oracle, Sybase, SQL Server, MySQL, DB2-LUW, PostgreSQL and Ingres).
General architecture diagram dbSQWare™ (when the SQWareProduction™ module is locally installed)
