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, 2 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...

SSIS can do it - you do need to ensure you set the Text Qualifier to Double Quotes

on those items mentioned, dv360_Line_Item_ID, Date and Event look unique - but you would need to check all your data.

normally you would analyze the data by doing group by in...

use a construct like the following

select *
from tablename
cross join (select hashbytes('SHA1', concat(field1
               ...

I say again - you will never remove that warning from your plan unless the underlying type is the same as your destination column

stop wasting time on things that can't...

that individual its a waste of time - even the last comment - how to fix that particular conversion to code - was told how - can't do it obviously...

you are never going to go past that error - you are converting from a nvarchar(255) to an int - to avoid the issue you will need to change the...

you likely also should change the BatchSize - 10k is normally way short of the best value - and optimal value also depends if your destination table is a HEAP,...