问题描述
在一家本地金融机构，我被他们的程序员斥责，因为他们表达了我的观点，即(他们的程序员痴迷于)(b)锁定他们的 MS SQL Server 2005 OLAP (SSAS) 数据库中的问题并没有多大帮助对我来说很有意义.(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 (SSAS) 数据库仅用于读取(部署后只读)，那么 OLAP 处理中的锁定问题是什么?
What are locking issues in OLAP processing if OLAP (SSAS) databases are used only for reading (read-only after deployment)?
在 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 中的锁定问题?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！