One of my SQL databases is growing out of control and its required nightly backups (FULL) are sucking disk space at a rapid rate. The backups are now at 120GB a pop and the DB itself is somewhere at 119GBs in size. We've tried shrinking/truncating the transaction logs but it doesn't seem to do anything. Being that I'm not the one who performs the transaction log shrinking when we need to, I'm not sure if doing this shrink operation is the same as having a Shrink Database task in a maintenance plan (is it the same?). I'm aware it's not usually recommended but we've been trying pretty much everything without success.
Short of cleaning the actual database of unused content, etc., is there anything else we can do via SQL Server?
Thanks!
Rob