I agree. ^.^ I'm trying to track it down and fix it hopefully.

I tried that just now, it resolves to a good name. I wonder why it states system.dbnull I cannot figure that one out.

These are Multiserver jobs. Though, even when...

Yeah... This is my new project.

It would be if our org didn't disable the standard trace to setup a custom one.

Sadly I think our "custom trace" omits these results. I'll have to add it back for future use.

Final question to add, is it better to fix the partition issue where the final partition is massive, or is there any gain over just adding 5 new files to...

I'm looking for something specifically like...

We'll call the partition PF_Help ^.^;

alter partition boundary_id value = 75000000

the question I guess is, will I expect dataloss if i just change the value?

currently...

notice it's the same person asking. ha.

Everything we can use a compressed backup on, we do. I've not seen any instances that there was an increased chance of corruption due to compression. Again, that's personal use....

No worries. They can get lost in time. Glad to help ^.^

http://www.sqlservercentral.com/Forums/Topic777462-169-1.aspx

This is a previous link that has this exact same issue.

My understanding is that even uncompressed backups do not backup "Free space". so where ever this bak came from... check the actual mdf/ndf file sizes. the space used data space...

Restores are faster, less Disk I/O.

Cost of storage on tapes or san or where ever you store (less space needed)

I honestly cannot think of any CONS for backup compression...

Higher CPU...

Wonderfully worded advice opc.three. ^.^

you will need your full and your differential to restore so you would need both files. If the file is the same size or say 10% +/- of it... I...