SQL Server and Azure SQL
Aviation Operations Software
Design and improve SQL-backed data access for dependable, responsive operational applications.
What this bullet means
This goes beyond basic database use: schemas, queries, stored procedures, migrations, and performance decisions should support real workloads.
Sample app idea
Operations Data Review Hub with SQL Server-style tables for flights, fees, invoices, adjustments, and reporting views.
Main build outline
- Create relational tables for operational events, rate rules, invoices, adjustments, and reporting periods.
- Add Entity Framework models and migrations for the core relationships.
- Write queries for open invoices, rate changes, monthly revenue, and activity by airport.
Portfolio proof
- Database diagram showing core relationships and reporting views.
- Sample SQL queries or EF Core query code for operational and billing reports.
Minimal documentation
- README with the business problem, screenshots, setup notes, and technology stack.
- One requirements note that maps the job bullet to the sample feature.
- One test plan note with happy path, validation, and edge case checks.
- One honest portfolio note that says this is self-directed practice, not employer work.
Modern .NET stack
- Blazor Server or ASP.NET Core Razor Pages.
- C# services with validation and dependency injection.
- SQL Server locally, then SmarterASP SQL Server or Azure SQL.
- Optional Azure App Service, GitHub Actions, Docker, and AI helper feature.