Imagine this. Your database transaction log has grown tremendously. You don't have enough space to do a backup of it and proper truncation. You do, however, have a backup of your database and are sure that you can restore it without any issue. What can you do? Here is a script that I use to force shrink transaction logs. Note that this can potentially be harmful, so make sure that you have a working backup of your database. Having said that, I've done this on a number of log files, some growing up to 200GB big, and I've not had any problems whatsoever. Replace the database_name variable in the first line with the actual name of your database (enclose in single quotes) DECLARE @DBName nvarchar(100) = ' database_name '; -- Declare the variable to be used DECLARE @sql nvarchar(1000), @exec nvarchar(300), @logfile nvarchar(100); -- Initialize Exec StoredProc SET @exec = QUOTENAME(@DBName) + '.sys.sp_executesql' -- Get Logfile name SET @sql = 'Se...