I haven't really done much with SQL Server 2005. I'm getting myself in the situation where I must, though, as I am using it as the platform for capturing performance counter data. I let the database grow way out of pocket and am now suffering the consequences. I know back with SQL Server 2000 you could use the osql utility to run commands and scripts from the command line. Looks like you do the same thing using sqlcmd for SQL Server 2005.

I'll probably be using this to execute a command file to shrink the transaciton log when it gets too big. I'll be using Performance Monitor's Alert feature to detect when the script needs to be run and have the action be to log a record in the application event log and to execute the script to truncate the log. The other alternative is to use SQL Server Agent to execute a cleanup script in a more meaningful manner. Consider my first suggestion a failsafe.