https://github.com/jschicht/LogFileParser

Parser for $LogFile on NTFS
https://github.com/jschicht/LogFileParser

Last synced: 5 months ago
JSON representation

Parser for $LogFile on NTFS

• Host: GitHub
• URL: https://github.com/jschicht/LogFileParser
• Owner: jschicht
• License: mit
• Created: 2014-02-19T21:34:57.000Z (about 11 years ago)
• Default Branch: master
• Last Pushed: 2023-11-27T22:38:20.000Z (over 1 year ago)
• Last Synced: 2024-08-03T22:15:05.130Z (8 months ago)
• Language: AutoIt
• Size: 31.9 MB
• Stars: 184
• Watchers: 21
• Forks: 30
• Open Issues: 2
• Metadata Files:
  • Readme: readme-logfile-mysql.txt
  • Changelog: changelog.txt
  • License: LICENSE.md

Awesome Lists containing this project

• jimsghstars - jschicht/LogFileParser - Parser for $LogFile on NTFS (AutoIt)

README

        
As of version 2.0.0.24, the output csv of LogFileParser supports import into MySql database. Attached is the database schema, logfile.sql, which should be used to create the database on MySql 5.6.4 or higher. That version is when precision in the timestamp was added. Earlier versions can be used, but then all DATETIME(6) occurrences in mft2csv.sql must be replaced with VARCHAR(28). It is important to use timestamp format 6. Precision of MilliSec or NanoSec is optional, but recommended. If NanoSec precision is used, then precision separator 2 must be empty (default value). It is also important to keep the timestamp error value to something valid for MySql, which the default value is. A nice sql client to use is HeidiSql. To import the csv into the database, use the import-csv.sql. Remember to change the path to csv at the top of file, and also the separator if the default was changed. Alternatively just use the autogenerated sql that will have correct settings anyway.

For manual database creation use following statement:

CREATE DATABASE IF NOT EXISTS Ntfs

	CHARACTER SET 'utf8'

	COLLATE 'utf8_general_ci';