Happy New Year. 2020 looks promising, sofar SSIS started working again in VS2019

Happy holidays! Awaiting the reviews of the lastest star wars. Already missed Han Solo

Odd question, have you contacted the CRM-provider about the slowness?

Testcase

Use case:
Deleted primary key detection
Method: Copy PK from Oracle to SQL Server and compare

Problem: starts fast but slows in speed every fetch?
Expected duration: 3000 seconds , network...

Hmm, contact microsoft support? Assuming the product is https://docs.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard

You could explore the Azure datafactory, flows and databricks

Thanks Steve Jones for the article. After uninstalling native client the 2019 worked

Where is that passage "Not if using Standard edition as clearly stated on the licensing guide" in the licensing guide?

Given it is RTM, I would at least expect that the installer works or notifies about the requirements

Wanted to try the new shiny SQL Server 2019. Install failed midway because some dependancy. System config checker is allright.

Detailed results:
  Feature:    ...

I hope CLOG.RecvdDate is not a string

WHERE CLOG.RecvdDate >=DATEADD(DAY,-1,convert(date,getdate())) and CLOG.RecvdDate<convert(date,getdate()))

I'll will try splitting it up.

The bottleneck is currently ssis or the sql destination. The source can deliver the data very vast (network spike) and then waits for ssis or...

Thanks for the recommendation. In progress of tuning the fetchsize from 50000 (semi-halt at 140 million records) to 10000. 500000 crashes the driver (unexpected termination)

I surely like the trend of cross-platform, opensource course of MS. There is also some cool stuff showing dependencies in Azure with log analytics. Regarding VS2019 they've added some profiling....

Eirikur Eiriksson, sorry to hear about your crystall ball. I hope it cristallizes again. Perhaps with the hourglass bbq of Steve.