Take the 2-minute tour ×  Current database is almost 200GB
however the transaction log file is only 4.1GB. I am worried if
this influences the performance of databse and how could it be
solved.  When I do this query  DECLARE @DatabaseName VARCHAR(50)
;   SET @DatabaseName = 'dbname'   SELECT name ,
recovery_model_desc ,   FROM  sys.databases   WHERE name =
@DatabaseName  Show Recovery Model = Simple, Log Reuse Wait =
Nothing.   Anyone has a knowledge why the log file is so small,
and does this influences on the performance?  share|improve this
question  migrated from stackoverflow.com Oct 15 '12 at 2:23
This question came from our site for professional and enthusiast
programmers.  3 Answers 3  The file size of the transaction log
is in no way related to the size of the data files, so the
question you've asked is really a non-starter to troubleshoot
performance.  The transaction log stores the physical operations
that happen to the database. Since the database is in SIMPLE
recovery, the log only holds on