3 posts tagged with "SQL Server"

Image by @abrizgalov

Overview​

Consider developing an application that requires you to store and retrieve data and display it on UI. You will likely need two things:

1. Relational Data Management System (RDBMS) allows you to store and retrieve data permanently on disk(s) with specific promises.
2. .NET is cross-platform, which allows you to develop different types of applications (web, console, mobile) using multiple languages (C#, F#).

Data Access in this context means making these two things (.NET & RDBMS) talk with each other. Users will interact with UI which is built using the .NET platform, which is going to learn how to talk with the database in its language (SQL).

.NET offers two different approaches to achieve data access?

• EF Core - An OR/M.
• .NET Native abstractions - without an OR/M

Image by @isaacmsmith

Query Store allows you to monitor and troubleshoot queries. It also provides stats about runtime such as CPU, IO and Memory.

Enable Query Store with default configuration using below SQL. It is enabled at database level.

SQL Server Enterprise offers scalable memory optimized relational tables. Yes, all data inside table will be loaded in memory. In-Memory tables has two flavors.

• Durable - Offers ACID
• Non-Durable