A statistic (on a table, a column / a set of columns or on an index) provides information on:
– the table (number of lines, average size of a line, number of blocks/page, density),
– the distribution of values ​​for the column(s) (number of distinct values, number of duplicates, existence of null values, histogram of distribution of values),
– the composition of the index (depth, number of blocks, cluster ratio).

These statistics are used by the database optimizer to study the different execution plans that can be used for a query.
The optimizer (based on costs / CBO) chooses the best execution plan (least expensive) from the data calculated from these statistics on, in particular, the number of rows and blocks of data to be shuffled at each stage of these plans (access strategies).

Statistics are essential for the proper calculation of query execution plans. It is therefore essential that they are up to date to take into account changes to the data and therefore to the indexes, columns and tables.
Thanks to update statistics, the optimizer has reliable data to choose the best performing execution plan to serve data to applications.

Initially implemented exclusively in the Paris region, our software dbSQWare has since made its way.
It’s thanks to our users: their trust, loyalty and high standards.
The software is constantly evolving to meet customer needs.
This year, 6 patches have completed and enriched the 2022 version of dbSQWare.
The 7th will be released in a few days while waiting for the 2023 version…

Welcome to Alban Vassallo, our new database administrator!

Alban joined dbSQWare yesterday.
We are very happy with his arrival in the team.

16 years old !
16 years have passed since the idea of ​​developing software that could handle the day-to-day administration tasks of several different database engines was born.

Born of a real need for companies, faced with the same problem of setting up (and then maintaining) operating scripts for their DBMS, the project first appeared to be audacious, even utopian for some.
However, by dint of reflection and work, the software was created in 2007 respecting the specifications for 4 engines.
Today, 12 engines are supported.

Modular, dbSQWare is constantly evolving to follow technical developments and meet customer needs.
Thank you to our users for their trust and their solicitation, because it is for them and thanks to them that the software exists.

This evening, afterwork “Incontournable Avignon” organized by the CIP – Club Informatique Provence Méditerranée.

Our CEO, Michel Payan will give feedback on the use of design in software design. He will be accompanied by Aurélien Beguet from the Atrioom agency, with whom we collaborated during the redesign of the dbSQWare web interface.

Exchanges, conviviality and networking will be there.
Good Essential to all participants!
 
 
 

The city of Marseille is now a dbSQWare user.

We are very happy to be able to assist the DBAs of the city of Marseille in their daily tasks of operating, managing and maintaining the databases.

Thank you for your trust !

Michel Payan, our CEO, will be present at the COTER NUMERIQUE working group on September 15, 2022, at the Novotel Paris Center Bercy.
The event, which will begin at 9:30 a.m., will be punctuated by the intervention of different local authorities in the form of feedback with 20 minutes of presentation and 10 minutes of questions/answers.

Between 10:15 am and 10:45 am, the city of Chelles will give its feedback on the use of dbSQWare with the intervention of Geoffrey Dunglas, accompanied by Michel.

A big thank you to the city of Chelles for its trust and recognition.
Good event to all participants!

The dbSQWare team wishes you a very happy back to work 2022!

With beautiful professional projects, desire and a lot of success.

The 31st edition of COTER-NUMERIQUE (the 1st for dbSQWare) has come to an end.

A big thank you to all the decision-makers who came to meet our team during this show.
Discussing the management of database engines is always a pleasure for Séverine Payan and Michel Payan.

Congratulations to Antoine Trillard and his entire team for the organization and the quality of the event.
Looking forward to the next edition, in 2023, in Deauville.

Thank you also to our colleagues and partners for their great sympathy.

– “The environment copy, what is it for?”

The environment copy allows you to duplicate an environment and thus have 2 identical environments (same structure, same tables, same data) on 2 different servers.

The interest is to have, for example, a development environment identical to that of production (in the case where the prod environment is copied in dev) and to provide developers with a working base reliable and up-to-date before they start coding (Caution, it may be necessary to anonymize the data!).
In other cases, the environment copy can make it possible to put a test environment into production, if it has successfully passed all the validation stages, or to set up a DRP (Disaster Recovery Plan) on D-1.

Finally, if the duplication is done through backups, this makes it possible to validate their viability.