Here are few steps by which you can drive out your SQL database from recovery mode and perform action on it.
First step is to stop the SQL Services
Then change the location of log files
Start the Server services and makes databases offline
Place the log file in previous location
Now bring the SQL database Online
Within few clock pulse rate you can access SQL database and back to work.
Excellent waste of time, won't do much else.
If you were to follow that recommendation, then when SQL restarts it will mark the databases as recovery pending, because of the missing log. Take it offline, replace the log and bring it back online and SQL will run recovery on the database, from the very beginning. So if you were to do that after the DB had been in recovery for 4 hours, after doing that it will be back at the beginning of recovery, with 4+ hours to go. It definitely won't come online immediately.
Please refrain from posting advice on database recovery if you're not familiar with how SQL behaves.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass