了解内存限制和技术 [英] Understanding In-Memory Limits and Technology
问题描述
我在这个页面上看
https://docs.microsoft.com/de-de/azure/sql-database/sql-database-vcore-resource-limits-elastic-pools
内存中的内存大小适用于 BC_Gen5_8 40 GB 。
我对此有以下问题：
1。当使用OLTP模式时，40 GB的限制是固定的，这意味着我只能拥有x内存优化表，总共最多40 GB的数据？
2。当启动和停止服务时，内存数据消失，导致其不是永久性的，仅用于"临时"服务。例如，分析需要在我的"工作"期间加载。它是否正确？我正在考虑有一个存储在磁盘上的
in.-memory表，但是当启动SQL数据库实例时，表被加载到内存中！？
3。使用列存储模式时 - >理论上没有限制因为SQL Server只保存当前在内存中使用的数据，因此它可以超出限制。
最好的问候
Yavuz
祝你好运，< br /> Yavuz B.< br /> < br />
我在这个网页上看
内存内存大小为 BC_Gen5_8 40 GB 。
我有以下内容对此提出的问题：
1。当使用OLTP模式时，40 GB的限制是固定的，这意味着我只能拥有x内存优化表，总共最多40 GB的数据？
2。当启动和停止服务时，内存数据消失，导致其不是永久性的，仅用于"临时"服务。例如，分析需要在我的"工作"期间加载。它是否正确？我正在考虑有一个存储在磁盘上的
in.-memory表，但是当启动SQL数据库实例时，表被加载到内存中！？
3。使用列存储模式时 - >理论上没有限制因为SQL Server只保存当前在内存中使用的数据，因此它可以超出限制。
最好的问候
Yavuz的
I am looking on this page
https://docs.microsoft.com/de-de/azure/sql-database/sql-database-vcore-resource-limits-elastic-pools
The In-Memory memory size is for BC_Gen5_8 40 GB.
I have the following questions on this:
1. When using the OLTP mode then the limit of 40 GB is fix that means that i only can have x memory optimized tables with in total max 40 GB of data?
2. The in memory data is gone when starting and stopping the service cause its not permanent and only to use for "temporary" analytics for example and needs to be loaded during my "job". Is this correct? I am thinking about having an in.-memory table which is stored on disk but when starting SQL database instance the tables are loaded into memory!?
3. When using columnstore mode -> there is theoritically no limit cause SQL Server only holds the data which is currently used in the memory and therefore it can exceed the limit.
best regards
Yavuz
Best regards,<br/> Yavuz B.<br/> <br/>
解决方案I am looking on this page
https://docs.microsoft.com/de-de/azure/sql-database/sql-database-vcore-resource-limits-elastic-pools
The In-Memory memory size is for BC_Gen5_8 40 GB.
I have the following questions on this:
1. When using the OLTP mode then the limit of 40 GB is fix that means that i only can have x memory optimized tables with in total max 40 GB of data?
2. The in memory data is gone when starting and stopping the service cause its not permanent and only to use for "temporary" analytics for example and needs to be loaded during my "job". Is this correct? I am thinking about having an in.-memory table which is stored on disk but when starting SQL database instance the tables are loaded into memory!?
3. When using columnstore mode -> there is theoritically no limit cause SQL Server only holds the data which is currently used in the memory and therefore it can exceed the limit.
best regards
Yavuz
这篇关于了解内存限制和技术的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
