Add Errorlog importer in SQL Nexus

[PiJoCoder]

Testing Plan

1. Build & Deploy Verification

• Clean and rebuild the solution. Confirm ErrorLogImporter.dll is present in sqlnexus\bin\Release\.

2. Importer Discovery

• Launch sqlnexus. Open the Import form and verify "ERRORLOG Importer" appears under Options > Importers with Enabled checked by default.

3. Basic Import (SQLLogScout output)

• Point to a SQLLogScout output folder containing SERVERNAME_ERRORLOG through SERVERNAME_ERRORLOG.6.
• Click Import. Verify:
  • All 7 or more ERRORLOG files appear in the file list and show green progress bars.
  • tbl_ERRORLOG is created with all 7 columns (RowNum, LogDateTime, Process, Message, ErrorNumber, State, FileName).
  • The composite index IX_tbl_ERRORLOG_LogDateTime_RowNum exists.
  • All files' data is present (query SELECT FileName, COUNT(*) FROM tbl_ERRORLOG GROUP BY FileName — should return 7 rows).

4. Multi-line / Continuation Lines

• Query for entries where Message contains CHAR(13) or CHAR(10) (e.g., registry startup parameters). Verify continuation lines are correctly appended to the parent entry rather than creating separate rows.

5. Error and State Extraction

• Query

  SELECT RowNum, LogDateTime, ErrorNumber, State, Message 
  FROM tbl_ERRORLOG 
  WHERE ErrorNumber IS NOT NULL

• Verify that rows with messages like Error: 18456, Severity: 14, State: 38. have the correct ErrorNumber (e.g., 18456) and State (e.g., 38) values populated.

• Verify that non-error rows have NULL for both ErrorNumber and State.

• Also query with this to see summary stats on errors

  SELECT ErrorNumber , State, COUNT(*) ErrorCount 
  FROM tbl_ERRORLOG
  WHERE ErrorNumber is not null
  GROUP BY ErrorNumber, State
  ORDER BY ErrorCount desc

6. Re-import with "Drop existing tables" enabled

• Import the same folder again. Verify the table is dropped and recreated (no duplicate data from previous import).

7. Disabled Importer

• Uncheck Enabled under the ERRORLOG Importer options. Re-import. Verify ERRORLOG files do not appear in the file list and tbl_ERRORLOG is not created.

[PiJoCoder]

Tested general ERRORLOG import - works fine.
Also tested ERRORLOG that contain Deadlock information - looks good

[hacitandogan]

Tested with multiple different scenarios , memory status outputs , dumps , database recovery failures (hekaton) , import is working fine for all those