SQL Server Transaction Logs

[Derek Fabb]

We are running Endpoint Protection 14 with the SEM5 database on SQL Server 2014.

I have a question about the transaction logs.

We have two transaction log files defined, sem5_log1.ldf and sem5_log2.ldf.

These are both limited to 16Gb, and they exist on the same disk.

From my limited SQL Server experience I was always led to believe that having a single log file was best practice.

Is there anything in the product that leads us to having two log files?

Would there be any disadvantage to defining a single 32gb transaction log?

[Torsten Knorr]

Hi, I would recommend to ask this a Microsoft Support Team member or specialist and give him some facts about your environment.
From a current point of view, you need only one Transaction Log and you should it place to a different drive.
As you may have implemented necessary SQL Maintenance Tasks, your Transaction Log should be truncated frequently.

Thats all and i beliefe, Symantec support can't realy help here, as this is Microsoft SQL Server related.