whoever stored those in next likely caused them to be corrupted without repair.

zip files should have been stored as image or varbinary(max)

assuming they were stored correctly, e.g. no bytes have...

SSRS also uses outside SQL memory - but for many things (when executing queries and the likes) it fall under SQL memory.

on this I don't have details of how to...

If all of your code has NOLOCK - then enabling RCSI and not removing NOLOCK is just adding overhead for now useful purpose.  SQL Server will be maintaining...

only you can know what to allocate to each one based on the load each instance/process needs.

for info SSAS has 3 memory settings you will need to change - there...

SSIS and SSAS memory usage are totally separated from that of SQL Server - and the min/max memory settings on SQL do not affect those.

SSIS does not have a "max...

you need to expand at the VM level, then do the same at OS level.

Do not use it - period.

see https://www.brentozar.com/archive/2021/11/nolock-is-bad-and-you-probably-shouldnt-use-it/

if you truly have to use it and the business has signed off on allowing potential bad data then use the Transaction level.

NOLOCK vs...

you can try shrink in 100 or 200 GB at the time - not advisable but would work -

the truncateonly is here in case you get lucky...

fix the queries and the indexes  - based on your latest threads that is where your issue is and the sooner you do it the better for everyone.

possible changes - in addition to what I mentioned on the other thread.

table C_B_CONTACT - likely the clustered key should be changed to be based on PARTY_ID...

it can take days to shrink depending on how busy the db is.

and I would expand that command - prefer to be specific about which files get truncated and to...

I may be wrong but this would only prevent LOG file shrink - not data file (which I...

what exact command are you using for it?

Tom - that is the perfect example of WHY code reviews SHOULD be done - the reaction that individual had would also be a good pointer to go and review...

did you implement the indexes I mentioned on https://www.sqlservercentral.com/forums/topic/query-filling-up-tempdb ?

some of them would help on this particular issue as well.

and while not necessarily the issue on this case replace that...