The default storage provider uses the file system to store .journal and .snapshot files. Release 0.5.0 introduced support for alternative storage provider modules. The sql storage module is a available as a separate download.
Using Sql Storage allows you to benefit from all the reliability and maintainability features of an RDBMS. Also, the journal can be examined/manipulated using regular SQL. The provider creates a single table named CommandJournal with the following columns:
Name | Description |
---|---|
Id | The unique sequential id of the command |
CommandName | The type name of the command executed |
Created | The point in time when the command was executed |
Entry | The serialized JournalEntry<Command> object |
Release 0.1.0 was tested on Sql Server 2008 R2 developer edition and should work with 2005, 2008, 2012 and SqlCE.
SqlEngineConfiguration
when creating or loading your databaseAlternatively, you can set Location
to a connection string directly. If so, you must also set the LocationType
and ProviderName
properties:
Use the StorageUtility to copy an existing journal from file to sql or sql to file.