The optional SQL directory contained a single PostgreSQL script with no
clear organisation. As we now have scripts for both PostgreSQL and MSSQL,
and multiple test scenarios (message generation, room creation, performance
testing), a clearer structure is needed.
Reorganises into postgresql/ and mssql/ subdirectories with descriptive
filenames that indicate purpose rather than execution order. Adds README
documenting available scripts and usage patterns.
Key scripts preserved:
- 410k message generator (PostgreSQL + MSSQL)
- 50 room creator with message redistribution (PostgreSQL + MSSQL)
- 10,000 minimal rooms for scale testing (PostgreSQL)
- 200 rooms with realistic affiliations and messages (PostgreSQL)
- Worker count configuration template (PostgreSQL)
Utility SQL scripts for debugging, performance testing, and scenario recreation shouldn't run automatically but should be available in the repository for developers to use when needed.
The optional/sql/ directory holds these scripts separately from
deployment-specific sql/ directories, which are mounted to PostgreSQL's docker-entrypoint-initdb.d. This avoids duplicating utility scripts across deployments whilst keeping them discoverable.
Each script includes a header with compatibility information and usage instructions. Users can either copy files to their deployment's sql/ directory for automatic execution on fresh start, or run them manually against a running database.
Matthew Vivian