next update:

if i watch the CPU in taskmanager, after i openend processes in activity monitor, the vCPUs goes from 10 % to 30%. So it seems that the query...

I don't know about the backups, this concerns (only) my db-Admin. He restored some dbs, so that seems to work 😉

but when I copy a big chunk of data,...

wait, Wellen_reiter, is this a VMWARE server?

SOS_SCHEDULER_YIELD is typical of CPU pressure - particularly where a VM instance is sharing CPU with other instances (VMware tries to be clever about...

sql will start off using minimum memory - then as you run more queries then the mem usage will go up (data pages being put into buffer cache)

general rule of...

Do you know if the log file is increasing significantly during the data import? I think 'bulk logged' recovery mode is sometimes used in this situation. Sorry I can't...

just wanting to check - 20GB purely for OS and 18 purely for SQL - so a total of 38GB ?

Thanks for that posting - it was a good reminder that we have to be more cautious and less trusting when traveling. I'd like to thing everyone is as...

DOH!!!! double facepalm moment

multiple copies of management studio open (I have v17 because it still has debug mode and v18 because I have sql2019)

executed a query thinking it was on...

looks like it's tried to apply "parallelism" (not quite the correct word, but it will do) to the function - this is possibly a result of the new scalar...

this sounds like a buffer cache issue - sometimes fast, sometimes slow, depends on if it is in cache...if not then it could be a recompile?

How much RAM on that...

looks like it's tried to apply "parallelism" (not quite the correct word, but it will do) to the function - this is possibly a result of the new scalar value...

big difference in the plans - it explains quite a lot

scrap that - I tried it and it's still an issue

looks like the assertion to the return variable is stopping at the first row within  a scalar function (ask Microsoft)...

Hi Grant,

That's the point, the statement does include an ORDER BY.

See my first post.

CREATE FUNCTION [dbo].[fnTest]()
RETURNS int
AS
BEGIN
       declare @myNumber INT;
...

This isn't what I'd call a change in behavior. It's always been stated, for decades now, that you can't rely on the order of rows without an ORDER BY...