<div>
For now truncate the log by shrinking it after that take a full database backup. Steps are<br />
<br />

<pre><code class="code-10 nolinks" id="code-20-42358923-1"><span>--</span>
<span></span>
<span>USE yourDBName</span>
<span>BACKUP LOG yourDBName WITH TRUNCATE_ONLY</span>
<span></span>
<span>DBCC SHRINKFILE (YourLogicalLogFileName, 30 ) </span>
<span></span>
<span>BACKUP DATABASE databasename TO DISK = 'Path\backupName.BAK'</span>
<span></span>
<span>--</span>
</code></pre>
<br />
Going forward you need to take regular log backup with your database backups.
</div>


<div>
@Pawan,<br />
<br />
I thought, WITH TRUNCATE_ONLY is deprecated since 2008. Could you please confirm.<br />
<br />
<a href="http://www.sqlserver-dba.com/2012/04/backup-log-with-truncate_only-is-discontinued.html" rel="ugc">http://www.sqlserver-dba.com/2012/04/backup-log-with-truncate_only-is-discontinued.html</a>
</div>


<div>
If this is on your local machine, do you even need to use the full recovery model? If you do not need point-in-time recovery for this database, consider changing the recovery model to Simple recovery.<br />
<br />
NOTE: Even if you use Simple recovery, your log file may still grow if you use long running transactions, perform operations on a large number of rows without committing, etc.
</div>


<div>
If that is in your local machine then change the database Recovery Model to Simple. Right click on Database node &gt;&nbsp;Properties &gt;&nbsp;Options &gt;&nbsp;On the right panel next to Recovery model: choose Simple &gt;&nbsp;Click OK. Now you can shrink the log file with this command:<br />
<br />
dbcc shrinkfile(&lt;logical_log_fi<wbr />le_name&gt;,0<wbr />)<br />
<br />
You get the &lt;logical_log_file_name&gt; from the Properties windows, as above, under the File section. In Simple recovery mode the log file will be kept under control by the SQL server.
</div>


<div>
Question abandoned.<br />
Closing via accepting these comments as solution.
</div>


<div>
<div class="content wysiwyg-content">
Error Occured in :Loln_spcustinstlmntdueUpT<wbr />oMonthMess<wbr />age : The transaction log for database 'SHRICITYREPORT' is full due to 'LOG_BACKUP'. Rollback Succesfully <br />
<br />
how can i retify this issue in my local maching iam running my sp &nbsp;shows log file full.
</div>
</div>


Error Occured in :Loln_spcustinstlmntdueUpToMonthMessage : The transaction log for database 'SHRICITYREPORT' is full due to 'LOG_BACKUP'. Rollback Succesfully 

how can i retify this issue in my local maching iam running my sp  shows log file full.

Log file full in sql server 2012

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.

Databases

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

SQL (Structured Query Language) is designed to be used in conjunction with relational database products as of a means of working with sets of data. SQL consists of data definition, data manipulation, and procedural elements. Its scope includes data insert, query, update and delete, schema creation and modification, and data access control.