Timeline for Microsoft SQL In-Memory OLTP in SQL Express 2019/2022
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 5, 2024 at 15:37 | history | became hot network question | |||
| Sep 4, 2024 at 21:43 | history | edited | Jurgen Cuschieri | CC BY-SA 4.0 | fixed syntax mistake |
| Sep 4, 2024 at 21:42 | vote | accept | Jurgen Cuschieri | ||
| Sep 4, 2024 at 17:06 | answer | added | Sean Gallardy | timeline score: 10 | |
| Sep 4, 2024 at 16:19 | comment | added | Jurgen Cuschieri | thank you for the heads up guys. I had not thought about this. I was aware there were memory limitations but I did not think it was only 1.4gb. as I said in my previous comments, I was going to run some tests to compare, but I would not have gotten very far anyway it seems! the search continues for a suitable "in-memory" store that can run natively on Windows :) | |
| Sep 4, 2024 at 16:13 | comment | added | Tibor Karaszi | Memory optimized tables are all about throwing lots and lots and lots of memory on your SQL Server. Express has a very low memory cap, so the whole idea seems like a no-go to me. In addition, you are attempting something that "nobody else in the world" are doing. Do you want to be the one to find all the issues with this feature on Express, filing case after case with MS? I wouldn't put myself in that position. :-) | |
| Sep 4, 2024 at 16:04 | comment | added | Jurgen Cuschieri | I haven't determined anything yet. I am at a point of consideration and I am looking at other technologies as well. I had prepared a testbed to run comparisons with normal SQL but due to these issues I did not proceed with the tests. | |
| Sep 4, 2024 at 15:25 | history | asked | Jurgen Cuschieri | CC BY-SA 4.0 |