Two Minute Drill: RELOG.EXE

Following on from last Two Minute Drill: LOGMAN.EXE, today's topic is the RELOG.EXE utility.  RELOG.EXE creates new performance logs from data in existing performance logs by changing the sampling rate and / or converting the file format.  RELOG.EXE is not a new tool - it is however one of those tools that most administrators are not […]

Following on from last Two Minute Drill: LOGMAN.EXE, today's topic is the RELOG.EXE utility.  RELOG.EXE creates new performance logs from data in existing performance logs by changing the sampling rate and / or converting the file format.  RELOG.EXE is not a new tool - it is however one of those tools that most administrators are not aware of.  Although RELOG.EXE is a fairly simple tool, it is incredibly powerful.  Let's look at the built-in help file for RELOG.EXE:

RELOG <filename [filename ...]> [options]

Parameters:
  <filename [filename ...]>     Performance file to relog.

OptionDescription
-?Display context sensitive help
-aAppend output to the existing binary file
-c <path>Counters to filter from the input log
-cf <filename>File listing performance counters from the input log.  The default is all counters in the original log file
-f <CSV | TSV | BIN | SQL>Output file format
-t <value>Only write every nth record into the output file
-oOutput file path or SQL database
-b <M/d/yyyy h:mm:ss [AM | PM>Begin time for the first record to write into the output file
-e <M/d/yyyy h:mm:ss [AM | PM>End time for the last record to write into the output file
-config <filename>Settings file containing command options
-qList performance counters in the input file
-yAnswer yes to all questions without prompting

Full Article