We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The first step is ensuring you are on compatibility level >=130. Run this query to find out the current compatibility level:
SELECT compatibility_level FROM sys.databases WHERE name = DB_NAME();
Check if In-Memory OLTP is supported for this server edition and database pricing tier. This has to be 1.
SELECT CAST(SERVERPROPERTY(N'IsXTPSupported') AS BIT) AS IsXTPSupported
Next, list tables where this is switched on:
SELECT SCHEMA_NAME(schema_id) SchemaName, name TableName FROM sys.tables WHERE is_memory_optimized = 1;
For any memory-optimised tables
-- EF Core 6 modelBuilder .Entity<Blog>() .IsMemoryOptimized(); -- EF Core 7 modelBuilder .Entity<Blog>() .ToTable(b => b.IsMemoryOptimized());
More info microsoft and red-gate and github
The text was updated successfully, but these errors were encountered:
Completed
Sorry, something went wrong.
Released in v3.8.1
sjh37
When branches are created from issues, their pull requests are automatically linked.
The first step is ensuring you are on compatibility level >=130. Run this query to find out the current compatibility level:
Check if In-Memory OLTP is supported for this server edition and database pricing tier. This has to be 1.
Next, list tables where this is switched on:
For any memory-optimised tables
More info microsoft and red-gate and github
The text was updated successfully, but these errors were encountered: