Relational databases and SQL

What this bullet means

The employer wants someone who can model real business records, write useful queries, and understand relationships between campaigns, creators, brands, metrics, and purchases.

Sample app idea

Influencer Campaign SQL Tracker with brands, campaigns, creators, posts, impressions, engagement, and verified purchase records.

Main build outline

1. Create relational tables for brands, campaigns, creators, posts, metrics, and purchases.
2. Add foreign keys that connect campaigns to creators and creator posts to metrics.
3. Write queries for campaign totals, creator performance, and engagement by category.
4. Add seed data that looks realistic but does not use private company data.
5. Document the schema and include two sample SQL queries.

Portfolio proof

• Schema diagram or table list in the README.
• Two sample SQL queries for campaign and creator performance.
• Screenshot of seeded campaign data in the app.

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.