Why should you care?

Indian enterprise .NET teams standardize on SQL Server or Azure SQL for ShopNest-style OLTP — the provider generates correct T-SQL and understands identity columns.

See it live — copy this example

Paste into a .NET project with EF Core packages, then run with LocalDB/SQL Server (dotnet ef / dotnet run).

services.AddDbContext<ShopNestDbContext>(options =>
    options.UseSqlServer(
        configuration.GetConnectionString("ShopNest"),
        sqlOptions =>
        {
            sqlOptions.EnableRetryOnFailure(maxRetryCount: 3);
            sqlOptions.CommandTimeout(30);
        }));

What happened?

• UseSqlServer activates the SQL Server dialect provider.
• EnableRetryOnFailure retries transient Azure blips.
• CommandTimeout caps long-running commands.

Practice next

1. Install SQL Server Express or confirm LocalDB from Visual Studio.
2. Connect once with SSMS or Azure Data Studio to validate the server.
3. Add UseSqlServer with retry policy for cloud readiness.
4. Set sqlOptions.UseCompatibilityLevel(120) only if you must support older SQL Server.
5. Log connection.Database from a scoped endpoint after CanConnectAsync succeeds.

Remember

UseSqlServer selects the SQL Server provider. LocalDB is sufficient for course labs. Retry and timeout options harden cloud deployments.

ShopNest on Azure SQL

Production ShopNest uses the same UseSqlServer call with EnableRetryOnFailure against Azure SQL Database.

Outcome: Brief network glitches retry instead of failing checkout immediately.