Truncate tables compromise backups

Production RiskSoftware ResiliencyCode Reliability

Truncate tables compromise backups

This code insight detects the total number of database objects containing code: SP, Functions, and Triggers. 


Why you should care

Although “truncate table” statement can be desirable under some circumstances from a performance point of view it is problematic because deletion are not logged. Thus the log backups become useless.

Business Impacts

Truncate tables increase risks from a productivity standpoint because it eliminates backups in code which can greatly setback projects.

Production Risk

CAST recommendations



About CAST and Highlight’s Code Insights

Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.

See featuresHow it works