Skip to main content

Questions tagged [memory-optimized-tables]

Memory Optimized Tables typically refer to tables where the rows in the table are stored in the server's RAM.

1 vote
0 answers
81 views

Context Aside from victims of latch contention, everybody gave up on memory-optimized table variables pretty quickly. Probably around the time they realised that they still don't have statistics. Yet, ...
J. Mini's user avatar
  • 1,342
1 vote
1 answer
98 views

I am using SQL Server 2019 Enterprise Edition. We have an in-memory database used for session state data with one table stored in memory, schema only durability, simple recovery, differential backups ...
Kathy S's user avatar
  • 11
0 votes
1 answer
94 views

Suppose that you have a table which is: Read from so frequently that it is almost always in RAM. Very small. Almost never changed. Is there any disadvantage moving such a table to in-memory OLTP? My ...
J. Mini's user avatar
  • 1,342
0 votes
1 answer
94 views

I have defined an In-Memory Table Type to hold a sequence of unique integers for the purpose of passing them between stored procedures. The type has the following definition: CREATE TYPE [dbo].[...
Dan Def's user avatar
  • 165
6 votes
1 answer
397 views

I am trying to use SQL In-Memory OLTP. The limitation is that the solution needs to be compatible with SQL Express 2019 and 2022. This link claims that In-Memory OLTP is compatible with all versions ...
Jurgen Cuschieri's user avatar
1 vote
0 answers
44 views

We've started using OLTP In-Memory tables (schema durability only) in a small DB (DB properties show 137 MB of Row data, 1GB of In-Memory data, BAK size of 152MB) and the recovery times (either ...
Hugh Clark's user avatar
0 votes
1 answer
153 views

In SQL Server 2019, you cannot put more than 32 GB of memory-optimized data in a database on Standard Edition. What happens if you try anyway? I'd try it myself, but I don't want to risk discovering ...
J. Mini's user avatar
  • 1,342
4 votes
2 answers
968 views

we use SQL Server 2019 on Windows with in-memory oltp activated on some databases. After a server reboot/service restart, the in-memory databases take very long to be available (more than an hour) ...
maxschaf's user avatar
0 votes
1 answer
711 views

Table variables have a bad reputation, mostly due to cardinality estimates. However, this reputation was earned before the introduction of memory-optimized table variables. Microsoft covers some use-...
J. Mini's user avatar
  • 1,342
0 votes
1 answer
139 views

I clearly have a missing piece in my understanding of in-memory OLTP. Suppose that I have a memory-optimised table that is set up to persist both schema and data. Given that these tables always live ...
J. Mini's user avatar
  • 1,342
0 votes
2 answers
780 views

I have a database with an in-memory filegroup that I want to remove (I won't go into many details why, but I want to move the database to another place without this filegroup). I'm trying to move the ...
dcop7's user avatar
  • 29
0 votes
0 answers
209 views

We have a DevOps pipeline for our DB Build/Release process and we're using VS SQL Database projects. We have one DB which makes extensive use of memory optimized table variables. Used for transfering ...
SqlNightOwl's user avatar
14 votes
1 answer
2k views

My version of SQL Server is SQL Server 2019 (RTM-CU18). The following repro code requires that an in memory filegroup is created. For anyone following along, please remember that an in-memory ...
Joe Obbish's user avatar
  • 33.3k
0 votes
0 answers
2k views

I use Memory-Optimized Table in my SQL Server. However the error "There is insufficient system memory in resource pool 'default' to run this query" occures after several drop/create/insert ...
Iga21207's user avatar
-2 votes
1 answer
170 views

I am wondering why this is coded this way. declare @messages table ([SEQUENCE_ID] BIGINT, [MESSAGE_ID] BIGINT PRIMARY KEY CLUSTERED ([SEQUENCE_ID])) ; delete T output deleted....
smartwombat's user avatar

15 30 50 per page
1
2 3 4 5
8