If you happen to be working on testing your client side caching of things like images and JS files, you might be banging your head against a wall wondering why you are not seeing any HTTP 304s being sent while analyzing the network traffic with the IE F12.  Those tools apparently suppress the browsers ability to cache these files, most likely to aid people who are debugging javascript from trying to understand why their changes aren’t being seen.  If you look at the Fiddler image below, you can see I loaded a site, which resulted in mostly 304s.  I then opened F12 in IE and reloaded the same site, and from that point on it avoided its cache and downloaded all the files.

If you just want to shrink your log files, you can use the following code, but make sure to replace DBName with whatever your real database name is.

USE DBName
ALTER DATABASE DBName SET RECOVERY SIMPLE
DBCC SHRINKFILE( 'DBName_log',1000 )
ALTER DATABASE DBName SET RECOVERY FULL

If by chance your log file isn’t named DBName_log, you can find out what the actual name is by using this bit of code:

USE DBName
SELECT name
FROM sys.database_files
WHERE type_desc = 'LOG'