question

HongruQi-5310 avatar image
HongruQi-5310 asked ·

SSIS ObjectRef Compatibility Issue

In the SSIS Dimension Processing Destination, there is an ObjectRef statement originally written in ASSL. However, it reports compatibility issue saying that the interface is not supported. Our DBA suggested that he attempted to upgrade Tabular model to SQL 2017 comp level worked, however is stuck on the ObjectRef statement in the SSIS Dimension Processing Destination, that requires new syntax in TMSL language, to reference dimension. And the project can be run on a SQL server without upgraded patch.

Can anyone help me with this problem?


9785-screenshot.png

azure-sql-databaseazure-data-science-vm
screenshot.png (74.1 KiB)
2 comments
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KalyanChanumolu-MSFT avatar image KalyanChanumolu-MSFT ·

Could you please post a screenshot for us to understand this issue better

0 Votes 0 · ·
HongruQi-5310 avatar image HongruQi-5310 KalyanChanumolu-MSFT ·

Hi, here is a screenshot of the issue.
9808-screenshot.png


0 Votes 0 · ·
screenshot.png (74.1 KiB)

1 Answer

KalyanChanumolu-MSFT avatar image
KalyanChanumolu-MSFT answered ·

From your description of the issue I gather that you have already performed the upgrade to Compatibility Level 1200. It is a one way upgrade and is not reversible.

If this is the case, the scripts that you run against the tabular models will need to be recreated using TMSL as well.


Here is the scripting language matrix for Analysis Services data models across different versions, at specific compatibility levels.

84473862-6e674900-aca7-11ea-8073-f34b89b813c4.png


2 comments Share
10 |1000 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HongruQi-5310 avatar image HongruQi-5310 ·

The issue started after the patch CU20 was applied to SQL Server 2017, it appears the Dimension Processing is no longer supported in Visual Studio. Our DBA suggests correcting the ObjectRef syntax for the Dimension Processing, but no guarantee it will work.



The current ObjectRef for the Dimension Processing in ASSL:
<Object xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">;
<DatabaseID>DatabaseTEST</DatabaseID>
<DimensionID>Query</DimensionID>
</Object>



Do you know what is the correcsponding syntax in TMSL?
Thank you!

0 Votes 0 · ·
KalyanChanumolu-MSFT avatar image KalyanChanumolu-MSFT HongruQi-5310 ·

Please check the Refresh command (TMSL) for the syntax. The examples section has the complete snippet.




The default behavior is to use as much parallelism as possible.

You can use the Sequence command (TMSL) along with Refresh to adjust the parallelism by tweaking the maxParallelism property






If this answers your query, please “Accept Answer” and Up-Vote for the same which might be beneficial to other community members reading this thread .
And, if you have any further queries do let us know. 

0 Votes 0 · ·