簡體   English   中英

如何將數據從MDX OLAP多維數據集“拉”到標准SQL Server表中?

[英]How can I 'pull' data from an MDX OLAP Cube into a standard SQL Server table?

已為我提供了訪問多維數據集的權限,並且需要知道是否可以設置一個可以連接到多維數據集並檢索內容(通過MDX查詢)的存儲過程。 我需要這樣做,以防止不得不從Management Studio或Excel(通過PowerPivot)導出數據。 我對多維數據集/奧拉普查詢非常陌生,因此請原諒我可能展示的任何天真之處。

最簡單的方法是創建一個鏈接的服務器,以多維數據集,然后從INSERT..SELECT OPENQUERY http://sqlblog.com/blogs/stacia_misner/archive/2010/11/30/31193.aspx

此選項的局限性在於

  • 它對MDX查詢有8000個字符的約束
  • 您必須為每個數據庫手動創建鏈接服務器
  • 結果為空時需要特殊代碼來處理
  • 結果集列中的數據類型過多(列為ntext,行為nvarchar(4000))

一個高級選項是ExecuteOLAP CLR存儲過程https://olapextensions.codeplex.com/

如果選擇使用OPENQUERY(最簡單的方法,但是有Brian所指定的限制),則以下過程可能很方便:

    /* 
PARAMS:
    @mdx: mdx statement
    @mdx_columns: specifies the mdx columns to retrieve from the executed mdx
    @linkedServer: linked server to be used
    @resultsTable: temporary table to hold results from mdx
    @resultsCols: if only some columns should be filled in @resultsTable, specify them here (e.g. '(col1, col2, ... )' )
    @expectedColCount: expected column count for mdx result. If actual column count is different from the expected count, no data is filled in
    @actualColCount: actual column count. Specify NULL if not interesed in this value
    @Debug: outputs debug info
*/
ALTER PROCEDURE [dbo].[exec_mdx_over_linked_server] (
    @mdx NVARCHAR(MAX),
    @mdx_columns NVARCHAR(1024) = '*',
    @linkedServer VARCHAR(64),
    @resultsTable VARCHAR(64),
    @resultsCols VARCHAR(1024) = '',
    @expectedColCount SMALLINT,
    @actualColCount SMALLINT = NULL OUTPUT,
    @Debug BIT = 0
)
AS
BEGIN
    SET NOCOUNT ON

    if (@Debug = 1)
        PRINT 'Started exec_mdx_over_linked_server procedure for populating ' + @resultsTable

    IF LEN(@MDX)>8000 RAISERROR ('MDX too long for openquery (exec_mdx_over_linked_server)', 
                                16,
                                1);

    declare @SQL NVARCHAR(MAX)

    IF (@Debug = 1)
    BEGIN
        -- getting results from mdx
        SET @SQL = 'SELECT ''Mdx results for ' + @resultsTable + ''' AS ''Mdx results'', ' + '*' + ' 
            FROM OPENQUERY(' + @linkedServer + ', ''' + @mdx + ''')';
        IF LEN(@SQL)>8000 RAISERROR ('MDX too long for openquery (exec_mdx_over_linked_server)', 
                                    16,
                                    1);
        EXEC (@SQL)
    END

    SET @SQL = '
        SELECT ' + '*' + ' INTO #resultsWithWeirdNameToAvoidTempCollisions
        FROM OPENQUERY(' + @linkedServer + ', ''' + @mdx + ''');

        SELECT @colCount = COUNT(*)
        FROM tempdb.sys.columns
        WHERE object_id = object_id(''tempdb..#resultsWithWeirdNameToAvoidTempCollisions'');

        if (@colCount = @expectedColCount)
            INSERT INTO ' + @resultsTable + @resultsCols + '
            SELECT ' + @mdx_columns +  ' FROM #resultsWithWeirdNameToAvoidTempCollisions'


    IF LEN(@SQL)>8000 RAISERROR ('MDX too long for openquery (exec_mdx_over_linked_server)', 
                                    16,
                                    1);

    if (@Debug = 1)
        PRINT 'dbo.exec_mdx_over_linked_server SQL = ' + @SQL

    DECLARE @colCount INT
    EXECUTE sp_executesql @SQL, N'@expectedColCount SMALLINT, @ColCount SMALLINT OUTPUT', @expectedColCount = @expectedColCount, @colCount = @actualColCount OUTPUT

    if (@Debug = 1)
    BEGIN
        PRINT '@expectedColCount = '; PRINT @expectedColCount
        PRINT '@actualColCount = '; PRINT @actualColCount
    END

    -- correction for small float numbers (< 10E-10)

    DECLARE @UpdateSql NVARCHAR(MAX) = N''
    DECLARE @SmallThreshold FLOAT = 0.00000000001


    SELECT @UpdateSql += '
                            UPDATE ' + @resultsTable + ' 
                            SET ' + QUOTENAME(COLUMN_NAME) + ' = 0 
                            WHERE TRY_CONVERT (FLOAT, ' + QUOTENAME(COLUMN_NAME) + ') IS NOT NULL
                                                 AND ABS(' + QUOTENAME(COLUMN_NAME) + ') < ' + CAST(@SmallThreshold AS NVARCHAR(30))
    FROM tempdb.INFORMATION_SCHEMA.COLUMNS with(NOLOCK)
    -- WHERE table_name like @resultsTable + '[_][_][_]%'
    -- changed, in order not to take into consideration objects from other spids
    WHERE table_name = object_name(object_id('tempdb..' + @resultsTable), (select database_id from sys.databases where name = 'tempdb'))

    IF (@Debug = 1)
    BEGIN
        PRINT '@UpdateSql = '; PRINT @UpdateSql;
    END

    EXEC (@UpdateSql);

END

它具有以下優點:

  • 處理收到的結果沒有預期的列(不執行任何操作)時的情況
  • 對很小的數字執行四舍五入(這可能會發生,因為多維數據集知道僅適用於浮點數)
  • 所有mdx語句都通過一個過程

分析時,我注意到大約。 100毫秒的開銷(通過過程執行,而直接對分析服務器執行)。

.NET開發人員可以使用ADOMD.NET框架,該框架允許運行參數化查詢並具有較小的開銷。

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM