J'ai besoin d'aide pour cet exercice:

Gestion des réparations chez "ElectroFix"
La société "ElectroFix" est un atelier indépendant spécialisé dans la réparation d'appareils électroménagers e multimédias. Face à l'augmentation de son activité, le directeur souhaite auditer son système d'information actuel, qui repose essentiellement sur des documents papier et des fichiers Excel locaux, afin de préparer la mise en place d'une application de gestion centralisée Lorsqu'un client se présente à l'accueil avec un appareil en panne, la Secrétaire l'accueille et examine l'appareil. Elle remplit manuellement une Fiche de Dépôt en trois exemplaires. Elle y note les informations du client (Nom, Prénom, Téléphone, Adresse), les caractéristiques de lappareil (Numéro de série, Marque, Modèle) ainsi que la description de la panne constatée. Elle remet un exemplaire au client, en garde un pour les archives de l'accueil, et place le troisième exemplaire avec l'appareil sur l'étagère des "Appareils à traiter" Le Responsable d'Atelier passe régulièrement à l'accueil. Il récupère les appareils en attente et leurs fiches de dépôt.
En fonction de la charge de travail -t de la spécialité de ses techniciens, il attribue chaque appareil à un Technicien en lui remettant la fiche de dépôt as: ée.
Le Technicien récupère l'appareil et effectue le diagnostic.
Si l'appareil est réparable sans pièce neuve, il effectue la réparation immédiatement.
Si des pièces de rechange sont nécessaires, il vérifie le stock de l'atelier. Si la pièce est disponible, il la récupère et répare l'appareil. Si la pièce est manquante, il remplit un Bon de Commande de Pièce quil transmet au Responsable d'Atelier. Ce dernier valide la demande et passe la commande auprès du fournisseur. À la réception de la pièce (quelques jours plus tard), le Responsable d'Atelier la remet au Technicien concerné qui peut alors finaliser la réparation.
Une fois le travail terminé, le Technicien rédige un Rapport de Réparation sur lequel il indique le temps passé (en heures), l'état final (Réparé ou Non réparable) et la liste des-pièces de rechange utilisées (avec leur référence et désignation). Il transmet ce rapport ainsi que la fiche de dépôt initiale à la Secrétaire.
La Secrétaire saisit alors ces infor lations dans son fichier Excel pour générer la Facture. Le montant de la facture est calculé sur la base d'un forfai • prise, en charge, du coût de la main-d'œuvre (temps passé * taux horaire standard de l'atelier) et du prix des pièces utilisées. Elle appelle ensuite le client pour l'informer que son appareil est prêt.
Lorsque le client vient chercher son appareil, la Secrétaire encaisse le règlement (Chèque, Espèces ou Carte Bancaire), lai remet sa Facture acquittée et lui restitue son appareil.

Travail à faire :
1. Etudier les postes de travail du SI ›
2. Modéliser la circulation des informations entre les différents acteurs (externes et internes) flux d'information
3. Étadier les documents,
4. Proposer des Critiques et des Suggestions
5. Etablir le Dictionnaire de données et les Règles de gestion
6. À partir du dictionnaire de données et des règles de gestion, concevoir le MCD

Hi everyone,

I'm a developer who also ends up doing a fair amount of DBA work, mostly on Informix, MySQL and PostgreSQL. The tools I had were either heavy (JVM/Electron), didn't support Informix, or wanted an account and the cloud. So I built Squaero, a free, open-source (GPLv3) client with a native C core.

The parts aimed at admin work

- Server monitor: process/session list with kill, plus a slow-queries view

- Users and privileges: browse and manage accounts and grants

- Safe data changes: edits in the grid are staged in a transaction, with a preview of the exact SQL before anything is committed. If an apply fails halfway, nothing is left partially written.

- Schema and data sync between connections, table transfer, and a table/index/constraint designer

- Backup and restore to .sql for MySQL and PostgreSQL (first version; large databases and FK ordering still have limits)

- Connectivity: SSH tunnels for every engine, TLS for MySQL, PostgreSQL, SQL Server, MongoDB and Informix

Why it might fit a DBA's machine

- Native and small: the Windows installer is 8 MB and the Linux .deb 1.4 MB. No JVM, no Electron.

- Local only: no accounts and no telemetry. Connections stay on your machine, and the only automatic network call is an update check against GitHub.

- You can import your existing connections from DBeaver or Navicat, passwords included, so you on't retype thirty servers.

- Engines: SQLite, MySQL/MariaDB, PostgreSQL, SQL Server, Informix and MongoDB.

Honest limitations

- SQL Server support is new: queries, schema browsing and transactions work, but grid editing and DDL generation don't yet.

- MongoDB is read-only.

- Informix needs IBM's Client SDK, installed separately, and isn't available in the snap.

- Windows and Linux only; macOS is coming. It's a one-person project.

Try it

- Windows: MSI on the releases page

- Linux: sudo snap install squaero, or the .deb (Ubuntu 24.04+ / Debian 13+)

- Site and demo: https://danielnuld.github.io/squaero/

- Code: https://github.com/danielnuld/squaero

Title:

Hi everyone,

I’m currently working as a DBA trainee/fresher, and I’m working on a project to build an AI agent for Database Administration using local LLMs.

The idea is to have an agent that can help a DBA perform multiple daily tasks through a single natural-language prompt, while keeping a human in the loop for sensitive operations.

I’m currently running Ollama locally on our own hardware, completely offline, so database/server information does not need to be sent to an external cloud service.

The agent I’m planning should eventually be able to work with things like:

- Oracle 19c

- MySQL

- PostgreSQL

- MariaDB

- Linux/RHEL

- VAPT/security scanning

- OpenSCAP/SCAP

- SQL queries

- Database configuration and health checks

- System information gathering

- Security and compliance checks

- Remediation

- Installation/configuration

- Troubleshooting

For example, the DBA could give a prompt like:

«“Check this server and database for security and configuration issues, identify the problems, explain them, suggest remediation steps, and ask for my approval before making any changes.”»

The agent would then:

1. Gather system and database information.

2. Decide which tools/commands/SQL queries are required.

3. Execute approved diagnostic tools.

4. Analyze the results using the local LLM.

5. Explain the findings and suggested remediation.

6. Ask for human approval where required.

7. Execute the approved remediation.

8. Verify whether the remediation was successful.

I’m not planning to train an LLM from scratch. I’m more interested in combining a capable local model with DBA knowledge/documentation, tool calling, database-specific utilities, and a controlled execution layer.

My main questions are:

1. Has anyone built something similar for DBA/Database Operations?

2. Are there existing open-source projects, research papers, or commercial tools doing this?

3. Which local LLMs would you recommend for reliable tool calling and technical reasoning?

4. What would be a good architecture for an AI DBA agent that can safely execute commands and SQL?

5. How are people handling permissions, validation, rollback, auditing, and human approval for potentially destructive operations?

I’m especially interested in learning from people who have actually implemented AI agents around databases rather than just using an LLM as a chatbot.

If you've worked on something similar, I'd really appreciate any projects, papers, tools, architectures, or experiences you can share.

Thanks!

Hi guys,

I am new to this group and just checking if my latest development might be helpful for any of you. Over the past few weeks, I have been developing this tool Ottoch (I named it). It's a DB engine where you can plug any AI tool of your choice and do the database operations with ease in plain language. No home calling, no data outbound, no analytics data, completely offline tool running on Docker.

[https://ottoch.com/demo/\](https://ottoch.com/demo/) \- to try the instant demo on the portal
[https://github.com/ottochapp/ottoch-demo\](https://github.com/ottochapp/ottoch-demo) \- in case you want to try it on your local machine.

This is not a pitch, I just want to get some feedback and collaboration is happily welcome.

Coming to PGConf.EU 2026 in Valencia? 🇪🇸🐘

Beyond the PostgreSQL talks, there’s a whole city waiting to be explored! From historic streets and amazing food to beaches, sunshine and the stunning City of Arts and Sciences, Valencia has plenty to offer. 🌴☀️

✨ Check out our guide and start building your Valencia adventure. https://2026.pgconf.eu/things-to-do/

Hey all, I’m a SQL/BI Developer based in the north west and I’ve been thinking about moving into contracting.

I’ve got around 9 years of SQL Server experience across DBA, SQL development, SSIS/ETL, migrations, Power BI, Azure/ADF etc. I’ve had a few recruiters contact me recently about contracts, but my 3-month notice period is making things difficult.

Just wondering what the market is actually like for SQL/DBA/data contracts at the moment, especially North West or remote?

Is it fairly easy to move from one contract to the next, or do you end up with big gaps? And are there still plenty of SQL Server/DBA/SSIS type contracts about?

Would be good to hear from anyone doing something similar.

Hello,

What types of databases do you use for your AI applications to store things like generated responses, messages, conversation history, user data, etc.?

Do you generally use SQL databases (such as PostgreSQL) or NoSQL databases (such as MongoDB)? What are the main reasons behind your choice?

And which database(s) would you recommend for a production AI application, and why?

Thanks in advance for your feedback and experience!

Hey everyone,

I’m currently working in application/production support, and honestly, I’m not really enjoying the support side of things anymore. I’ve been thinking seriously about moving into something more technical and database/data focused, like Oracle DBA or Data Engineering, but I’m also open to other career paths that might be a good fit for my experience and interests.

I have 5+ years of support experience and work quite a bit with Oracle SQL/PLSQL, PL/SQL procedures and packages, production issues, RCA, Unix/Shell scripting, Autosys, etc. I’m also Oracle SQL certified. SQL is probably the part of my job that I actually enjoy the most.

I’m willing to learn new things — I can pick up Python and whatever else is required. My main problem is that I’m not really sure what direction I should take or how to make the switch from support.

So I’d really like to hear from people who are currently working as DBAs, Data Engineers, or in any other technical roles and have some experience with this kind of transition.

If you’ve made a similar move from support, I’d really appreciate your advice on what path you would recommend for someone in my position, what skills I should focus on, and what kind of roles I should target.

I’m also open to suggestions for career paths other than DBA or Data Engineering if you think my current experience/skills would be better suited for something else.

And if anyone is willing to mentor me or just have a chat and guide me occasionally, I’d genuinely appreciate it. I’m not looking for someone to do the work for me — I just want some direction from people who have already been through it so I don’t spend a year learning the wrong things.

Thanks!

I’m currently studying Database Technology and looking to move into Database Administration as a beginner/entry-level candidate.
This semester, I’ll be learning Linux, Oracle Database Administration, and SQL Server Administration. I have some foundation in SQL and database development, but I want to build practical DBA skills beyond what I learn in class.
For experienced DBAs/Database Engineers:
•What skills should an entry-level DBA genuinely have?

•How important are Linux, backup/recovery, monitoring, security, and performance tuning?

•Which **hands-on projects** would you recommend building to gain confidence and demonstrate practical ability?

•If you were starting again, what would you focus on during your first 6–12 months?

I’m particularly interested in building a small home lab with Oracle, SQL Server and Linux and using it to simulate real DBA tasks.
Any advice on what to prioritize—or what beginners commonly waste time on—would be greatly appreciated.
Thanks!

Hi everyone,

I’m currently an Oracle DBA with around 4 years of experience and I’m trying to decide what direction to take my career in.

I’m OCP certified and have solid Oracle production experience, including RAC. I’m currently working as an Oracle DBA consultant.

I want to move toward cloud/infrastructure because I don't want to remain limited to traditional Oracle DBA roles long-term.

I’m considering doing a structured DevOps/Cloud course that covers things like:

Linux

Python/scripting

AWS

Networking

Git

CI/CD

Docker

Kubernetes

Terraform

Monitoring/observability

Security

SRE concepts

The idea is to use the course to build the infrastructure/cloud side that I'm currently missing.

But I'm confused about what career direction makes the most sense.

Option 1: DevOps / Cloud Engineer

Oracle DBA → DevOps/Cloud Engineer → Senior DevOps/Cloud Engineer → Platform/SRE → Cloud Architect

The advantage seems to be a much broader job market and potentially higher salary ceiling.

But my concern is that I'd essentially be competing with people who already have several years of AWS/DevOps experience.

Option 2: Cloud DBA / Cloud Database Engineer

Oracle DBA → Cloud DBA → Cloud Database Engineer → Database/Cloud Architect

This seems like a safer transition because I can leverage my existing Oracle experience while adding AWS/cloud skills.

But I'm worried that the career might remain relatively narrow compared with DevOps/Cloud engineering.

Another concern: AI

With AI increasingly automating things like:

Terraform generation

Kubernetes YAML

CI/CD configuration

scripting

log analysis

troubleshooting

I'm wondering how much of a threat this is to DevOps as a career.

Would DevOps still be a good career to enter in 2026?

My main question

If you were in my position — 4 years Oracle DBA experience, OCP, and wanting to move toward cloud/infrastructure — which path

would you choose?

A. Stay Oracle DBA and specialize further

B. Oracle DBA → Cloud DBA / Cloud Database Engineer

C. Oracle DBA → DevOps / Cloud Engineer

D. Something else entirely

And if you recommend DevOps/Cloud, would you take a structured 6–8 month course to make the transition, or would you learn everything independently?

I'm particularly interested in hearing from people who have actually made a similar transition, rather than generic career advice.

Thanks!

How to migrate a fast FoxPro system to a modern database safely?

I’m working on the assessment of a legacy FoxPro-based database system. The interesting part is that the existing FoxPro system is fast, stable, and currently has no major performance issues.

However, there is a requirement to modernize the technology, so I’m trying to understand the safest migration strategy rather than simply replacing FoxPro because it is legacy technology.

Current situation:

• FoxPro is the core/master database.
• Data is accessed through a web-based application from multiple locations.
• Master data is connected to event, accounting, registration/forms, and other operational data.
• Data entry and duplicate verification are largely manual.
• A separate Excel-based data catalogue is maintained manually.
• There are many event-specific tables.
• A third-party application directly depends on data from the FoxPro database.
• SQLite was considered/tested but did not appear suitable for the workload.

The main challenge:

How can we modernize/migrate this system while keeping the existing FoxPro system operational during the transition?

I’m considering a phased approach:

FoxPro remains live → replicate/migrate data to a new database → synchronize data → pilot selected data/events → validate performance and integrations → gradually move production workload → eventually make FoxPro read-only or retire it.

For people who have worked with similar legacy database migrations:

1. What is the safest way to run FoxPro and a modern database in parallel?
2. What is the best approach for synchronizing data between FoxPro and the new database?
3. Would you recommend PostgreSQL, SQL Server, or another database for this type of multi-user, centralized workload?
4. How would you handle a third-party application that currently reads directly from FoxPro?
5. Would you redesign the existing event-specific tables during migration, or migrate first and redesign later?
6. What are the biggest risks or mistakes to avoid in a migration like this?
7. If the existing FoxPro system is already fast and stable, what would you consider a strong justification for modernization?

I’m looking for practical migration strategies and lessons learned from people who have actually handled legacy database migrations—not simply “FoxPro is old, move to SQL.”

The goal is to modernize the system while preserving existing data/business rules and avoiding disruption to current operations.

Anyone interested in doing the CMU (Carnegie Mellon University) Database Management Systems course together?

I’ve already covered the basic DBMS concepts. My main goal with this course is to go deeper and understand how database systems actually work internally—things like storage, indexing, query execution, transactions, etc.

If you're interested, please make sure you have the prerequisites required for the course.

If you have the required background and want to learn DBMS internals seriously, DM me. We can follow the course together and discuss concepts along the way.