can you post the FULL entry of sysprocesses - all columns

@Grant Fritchey - pretty sure it is a cross database query (use db2, select from db1), so it should be using the same set of data and data structure,...

you should not be using that sysprocesses anymore and should instead be using one of the system views/functions. see https://learn.microsoft.com/en-us/sql/relational-databases/system-tables/mapping-system-tables-to-system-views-transact-sql?view=sql-server-2017

the format can vary depending on resourcetype - one of the...

ZIP files are binary files so will not save correctly as a string. Binary can be encoded as a string although the size will obviously be increased. One way...

where is the current data used by the Delphi system?

and how did you copy it into your new table (and as I said it should be varbinary(max))

and can you ask...

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