Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ This repository simulates a sales CRM/ERP database with real-world data defects

This is not a SQL syntax exercise. The goal is to show how to use SQL to **find real defects** in a database whose data is already corrupted, the way it would happen while investigating a bug reported in production.

> **Related project:** the follow-up is [sql-performance-investigation](https://github.com/ThomasTDS/sql-performance-investigation), built on the same CRM/ERP with a realistic data volume. There the data is correct but the query is slow, and the evidence comes from execution plans (`EXPLAIN ANALYZE`). Its reports are written in Portuguese.

> **About the data:** the whole schema and all the data are fictional, created specifically for this portfolio project. No information from any current or past employer was used.

> **About the language:** the investigation reports, the SQL comments and the database identifiers (table and column names) are in Portuguese. This README is a full translation of the [Portuguese README](README.md).
Expand Down
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ Este repositório simula um banco de dados de CRM/ERP de vendas com defeitos de

Não é um exercício de sintaxe SQL: o objetivo é demonstrar a habilidade de usar SQL para **encontrar defeito real** num banco com dados já corrompidos, do jeito que aconteceria investigando um bug relatado em produção.

> **Projeto relacionado:** a continuação é o [sql-performance-investigation](https://github.com/ThomasTDS/sql-performance-investigation), sobre o mesmo CRM/ERP com volume realista de dados. Lá o dado está certo, mas a consulta está lenta, e a evidência vem dos planos de execução (`EXPLAIN ANALYZE`).

> **Nota sobre os dados:** todo o schema e os dados aqui são fictícios, criados especificamente para este projeto de portfólio. Nenhuma informação de empregador atual ou anterior foi usada.

---
Expand Down
Loading