问题描述
在一个本地的金融机构我被他们的程序员为前pressing他们我看来责备他们（他们的程序员与痴迷）（二）锁定在他们的MS SQL Server 2005的OLAP问题（SSAS）数据库（S）并没有多大意义了我。 （该OLTP数据库的SQL Server，Oracle和非RDBMS ERP）。
In one local financial institution I was rebuked by their programmers for expressing them my opinion that (their programmers' obsession with) (b)locking issues in their MS SQL Server 2005 OLAP (SSAS) database(s) did not make much sense to me. (The OLTP databases are SQL Server, Oracle and non-RDBMS ERP).
什么是锁定在OLAP处理问题，如果使用OLAP（SSAS）数据库中的仅用于阅读（只读部署之后）？
What are locking issues in OLAP processing if OLAP (SSAS) databases are used only for reading (read-only after deployment)?
在这方面做这种（？一whic）出现问题 - SSIS处理，并从OLTP数据库中的数据传输过程中结果？
SSAS（OLAP）数据库的部署SSAS中？
In which context do such (an whic?) issues arise - during SSIS processing and transfer of data from OLTP databases?
during deployment of SSAS (OLAP) databases to SSAS?
这问题并不局限于到SQL Server。
This question is not restricted to SQL Server.
推荐答案
OLAP无论如何都不会限制为只读方案。如果你的系统数据层中从地面尺寸方面设计的，你可以用它进行分析处理以及用于CRUD操作。是的，你有可能会由于数据的一致性你在分析程序，提供面对一些锁的问题。
OLAP is not anyway restricted to readonly scheme. If your system' data layer designed in terms of dimensions from the ground up, you may use it for analytical processing as well as for CRUD operations. And yes, there you can face some locking problems due to data consistency you have to provide during analysis procedures.
如果OLAP是只读的那么同样的问题究竟出现在从OLTP转移。这是一个常见的错误是在这样的小块使得瓶颈尽快获取更新的数据为OLAP。
And if OLAP is readonly then the same issue arises exactly while transferring from OLTP. It's a common mistake to fetch updated data into OLAP asap in small chunks thus making bottlenecks.
这篇关于什么是OLAP锁定问题？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！