I think that knowing why and how that function is called so many times may help pointing you to a better solution.

how all those hierarchical rules are applied may also...

• This reply was modified 4 years, 2 months ago by frederico_fonseca.

SSAS memory settings are the culprit here.  In Enterprise edition, the memory limit for SSAS is the server max, so it is very probable that SSAS is competing against...

make sure that TCP/IP protocol is enabled on the sql instance -= need to do it on server itself

the query above would give an error with variable @FromDate as it is not declare WITHIN the @sql

if you are doing a exec @sql then this would fail - different...

likely your tabular server memory settings not setup correctly - these can be tricky and need to be set according to whatever memory is available to the particular tabular instance...

there are multiple things that can cause a connection to drop - increasing the timeout will not prevent those as it is only meant to prevent the timeout error itself.

for...

it means that if whatever command you are executing (a update/delete query or a exec of a SP, if it takes more than 30 seconds it will terminate its execution...

do execute (@query)

instead of having all your tables as heap and with additional non clustered indexes (columnstore or not) try and make one of them a clustered columnstore (or a normal clustered...

while looking into it - was there a reason for you to build a heap with columnstore indexes instead of making one of them a clustered columnstore index?

what is the compatibility mode of the database? - never mind - its 150.

Before trying anything else do a rebuild of the columnstore indexes on the tables used on the...

• This reply was modified 4 years, 3 months ago by frederico_fonseca.

use https://www.sentryone.com/plan-explorer - it has a option to anonymize the plan so all object names/columns get replaced with "object1, object2" and so on.

and put it on https://www.brentozar.com/pastetheplan/ and...

problem isn't VS 2022 - issue is that none of the SSRS options will work with .net core - mainly the report viewer which is a must have for many...

its always the same issue - dev does not have same volume as QA/Prod and what runs well in dev most times will not run well with volumes.

Just a small...

off course it can.

step 1 - set double quotes as text qualifier

step 2 - change the "numeric" column name << THE NAME itself>> to have double quotes around it

step 3...