Data
Disk & DatabaseDB is a broad database suffix. Some files are SQLite, but not every DB is. Identify the producer and avoid directly modifying an active application database.
- What it is used for
- Application data and indexes
- What the file contains
- Producer-dependent
All sections, questions and sources
Content reviewed： · Editor：Kai
Opening steps
Choose your environment or purpose to see its steps.
Menu labels and support vary by app, OS and version. Preserve the original before making changes.
Troubleshooting by symptom
- Wrong format: identify the system from origin/header information, not the suffix.
- Locked database: check active use rather than deleting locks or companion files.
- Missing recent data: journals/WAL may matter; use a supported backup workflow.
- CSV zeros disappear: inspect identifier type and spreadsheet import.
- Table missing: inspect selected DB, schema and export scope.
- Encrypted DB rejected: use the authorized source application/authentication.
Identified DB → CSV / backup
- Choose needed tables through the producer’s exporter or matching database tool.
- Verify counts, types, nulls, dates and related tables; preserve originals/backups.
- Verify exported counts/samples and retain a database copy for restoration.
CSV usually omits indexes, constraints, interfaces and application behavior.
Copying versus consistent backup
Prefer supported backups over copying an active database file; SQLite WAL may be part of its persistent state.
Example: investigate source backup consistency when recent updates are absent.
Source for these steps：SQLite Project · Database File Format / SQLite Project · Command Line Shell For SQLite / SQLite Project · SQLite Backup API / SQLite Project · Write-Ahead Logging
Preserve data and database structure
Keep the original/schema when indexes, relationships, views or application behavior must be restored.
Source for these steps：SQLite Project · Database File Format / SQLite Project · Command Line Shell For SQLite / SQLite Project · SQLite Backup API / SQLite Project · Write-Ahead Logging
Related-format differences
| Format / method | Role | What to verify |
|---|---|---|
| DB | Various engines | Producer/encryption |
| SQLite backup | Consistent database | Supported backup |
| CSV | Table export | Types/nulls/relations |
Handling and security
Databases may contain credentials/private data; avoid online conversion or replacing active data with manually altered copies.
Questions and answers
Is every DB SQLite?
No; identify its producer and format.
Is copying one file sufficient?
Companion files/active transactions may matter; use supported backups.
Does CSV restore the application?
It is not a full backup of application logic/structure.
May I delete the matching WAL file?
It may contain committed changes; use the application’s shutdown/backup workflow.
Does read-only mode open every DB?
Encryption, proprietary engines and versions still matter; identify the source first.
Format facts: name, steward and MIME type
- Formal name
- Producer-specific database file
- Steward / specification
- Producing application / database system
- MIME type
- Depends on the producer or server; an extension alone does not establish a MIME type.
Primary and official sources
- Project documentationDatabase File Format
Documents SQLite headers and companion journals.
SQLite Project · Link checked： - Project documentationCommand Line Shell For SQLite
Reference for database, SQL and CSV workflows.
SQLite Project · Link checked： - Official documentationSQLite Backup API
Consistent backups of an active database.
SQLite Project · Link checked： - Official documentationWrite-Ahead Logging
Database/WAL relationship and read-only conditions.
SQLite Project · Link checked：