So first of all I’m not a SQL expert. Secondly I don’t recommend performing this on a production system. Third, this actually won’t happen on a production system as long as you’re performing backups – and your backup solution supports MSSQL – and I hope if it *is* a production system that you are actually backing it up.<\/p>\n
Open the SQL Management Studio<\/strong> Run the following in the query window<\/strong> This will show you the name of the database and associated size of log files.<\/p>\n Assuming that the INSERTNAMEHERE database is the one eating through the space<\/strong> You can then run the logspace again and verify<\/strong> This all worked nicely on my development system that doesn’t require\/have backups in place.<\/p>\n","protected":false},"excerpt":{"rendered":" So first of all I’m not a SQL expert. Secondly I don’t recommend performing this on a production system. Third, this actually won’t happen on a production system as long as you’re performing backups – and your backup solution supports MSSQL – and I hope if it *is* a production system that you are actually … Continue reading Clear MSSQL Log Files<\/span>
\nConnect using the windows authentication piece, OR your SA password<\/strong><\/p>\n
\nDBCC sqlperf(logspace)<\/code><\/p>\n
\nUSE INSERTNAMEHERE;<\/code>
\nGO<\/code>
\nALTER DATABASE INSERTNAMEHERE<\/code>
\nSET RECOVERY SIMPLE;<\/code>
\nGO<\/code>
\nDBCC SHRINKFILE (INSERTNAMEHERE, 1);<\/code>
\nGO<\/code>
\nALTER DATABASE INSERTNAMEHERE<\/code>
\nSET RECOVERY FULL;<\/code>
\nGO<\/code><\/p>\n
\nDBCC sqlperf(logspace)<\/code><\/p>\n