Choosing the Right Indexing Strategy for SQL Server Workloads
A decision guide for SQL Server indexing strategies, comparing clustered, non-clustered, covering, and columnstore indexes to balance read performance and write overhead.
Loading…
ReadMeFeed / Community knowledge
#sql-server
Real questions. Useful conversations. Find the people who know your stack.
microsoftsqlserverClosing the Loop Between C# and SQL in JetBrains Rider
Stop jumping between your IDE and database manager. Learn how to use JetBrains Rider's database integration and language injection to validate SQL strings against live schemas.
dotnetUsing Query Store in SQL Server to Detect Plan Regressions
Query Store lets you capture every query’s plan and runtime stats in SQL Server, giving a durable baseline for performance tuning and regression detection. Enable it once, tune retention, and use plan_compare to spot regressions in production.
Architecting a Decoupled Data Access Layer in VB.NET with ADO.NET
Learn how to build a secure, decoupled Data Access Layer in VB.NET using ADO.NET, focusing on the Repository pattern, parameterized queries, and connection management.
Diagnosing and Resolving TempDB Contention in SQL Server
A diagnostic guide to identifying and resolving TempDB contention in SQL Server using wait statistics, I/O monitoring, and targeted configuration changes.
VB.NET ↔ ADO.NET: Transactional Rollback Scope for DDL Statements in SQL Server
When a Visual Basic .NET application uses SqlTransaction to wrap a schema change such as ALTER TABLE or DROP COLUMN , the goal is to determine whether the DDL can be rolled back if a later data manipulation step fails. The constraint is that SQL Server issues an implicit commit for most DDL commands, so the transaction started in VB.NET code does not encompa
visualbasicHow can I diagnose intermittent connection pool exhaustion in a .NET app using ADO.NET with SQL Server on Glitch?
The goal is to identify why a connection pool intermittently runs out of available connections in an ADO.NET‑based application hosted on Glitch, while using a specific pooling feature such as Max Pool Size. The application exhibits sporadic time‑outs and exceptions despite seemingly normal traffic, making it unclear whether the exhaustion stems from unreturn
glitchSQL Server PAGE-level restore and DBCC CHECKDB interaction: do repaired pages stay suspect?
The goal is to understand whether a page-level restore using RESTORE WITH PAGE automatically marks the repaired pages as clean, or if the pages remain listed in msdb.dbo.suspect_pages until a manual DBCC CHECKDB is executed. Constraints include version‑dependent behavior: in some releases the suspect_pages entry persists after RESTORE WITH PAGE, requiring an
EF Core Skip/Take pagination changes SQL translation across SQL Server compatibility boundaries
Entity Framework Core translates Skip and Take into provider-specific SQL, but the exact translation depends on the database compatibility level. On SQL Server, a Skip/Take query typically becomes OFFSET ... ROWS FETCH NEXT ... ROWS ONLY on SQL Server 2012 or a compatible compatibility level; older instances may produce a different SQL shape. This creates a
entityframeworkcore