問題描述

在一家本地金融機構，我被他們的程序員斥責，因為他們表達了我的觀點，即(他們的程序員癡迷于)(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 中的鎖定問題?的文章就介紹到這了，希望我們推薦的答案對大家有所幫助，也希望大家多多支持html5模板網！