Besides not doing that at all... my only advice would be that if you did... take a full backup afterward to start a new recovery chain.
I'm shocked at the number of times I've seen people suggest truncating a log file as if it were something trivial... I'm also shocked at the number of people who post about not having a good backup and needing emergency help in a crisis... probably the same people
:hehe:
What you are doing by shrinking files with the GUI is running a DBCC Shrinkdatabase or Shrinkfile.
Technical details are below.
Many people will caution against running these because they cause file fragmentation and consume massive amounts of resources (except the shrinkfile with truncateonly).
Shrinking logfiles is a better bet to free up disk space than shrinking a database. The SQL logfile is structured in a different way where it isn't affected (as much) by fragmentation. The only caveat is that if your logfile is ballooning all the time it probably wants to be that size... in that case I suggest more frequent log backups (and quickly getting those files to a remote archive) to keep disk use to a minimum.
Cheers!
~BOT
Craig Outcalt