--- 93_DbLog.pm	2021-03-27 10:43:08.301118729 +0100
+++ 93_DbLog.pm	2021-03-27 11:31:53.728334894 +0100
@@ -274,6 +274,8 @@
                                "colValue ".
                                "DbLogSelectionMode:Exclude,Include,Exclude/Include ".
                                "DbLogType:Current,History,Current/History,SampleFill/History ".
+                               "SQLiteJournalMode:WAL,off ".
+                               "SQLiteCacheSize ".
                                "dbSchema ".
                                "defaultMinInterval:textField-long ".
                                "disable:1,0 ".
@@ -3232,8 +3234,12 @@
     $dbhp->do("PRAGMA synchronous=FULL");    # For maximum reliability and for robustness against database corruption, 
                                              # SQLite should always be run with its default synchronous setting of FULL.
                                              # https://sqlite.org/howtocorrupt.html
-    $dbhp->do("PRAGMA journal_mode=WAL");
-    $dbhp->do("PRAGMA cache_size=4000");
+    if ( AttrVal( $name, "SQLiteJournalMode", "WAL" ) eq "off" ) {
+        $dbhp->do("PRAGMA journal_mode=off");
+    }else{
+        $dbhp->do("PRAGMA journal_mode=WAL");
+    }
+    $dbhp->do("PRAGMA cache_size=". AttrVal( $name, "SQLiteCacheSize", "4000" ));
   }
  
   return 1;
@@ -7635,6 +7641,40 @@
   <br>
   
   <ul>
+     <a name="SQLiteCacheSize"></a>
+     <li><b>SQLiteCacheSize</b>
+     <ul>
+       <code>
+       attr &lt;device&gt; SQLiteCacheSize &lt;number of memory pages used for caching&gt;
+       </code><br>
+
+       The default is about 4MB of RAM to use for caching (page_size=1024bytes, cache_size=4000).<br>
+       Embedded devices with scarce amount of RAM can go with 1000 pages or less. This will impact
+       the overall performance of SQLite.
+     </ul>
+     </li>
+  </ul>
+  <br>
+
+  <ul>
+     <a name="SQLiteJournalMode"></a>
+     <li><b>SQLiteJournalMode</b>
+     <ul>
+       <code>
+       attr &lt;device&gt; SQLiteJournalMode [WAL|off]
+       </code><br>
+
+       Determines how SQLite databases are opened. Generally the Write-Ahead-Log (<b>WAL</b>) is the best choice for robustness
+       and data integrity.<br>
+       Since WAL about doubles the spaces requirements on disk it might not be the best fit for embedded devices
+       using a RAM backed disk. <b>off</b> will turn the journaling off. In case of corruption, the database probably
+       won't be possible to repair and has to be recreated!
+     </ul>
+     </li>
+  </ul>
+  <br>
+
+  <ul>
     <a name="syncEvents"></a>
     <li><b>syncEvents</b>
     <ul>
@@ -9083,6 +9123,40 @@
   </ul>
   <br>
   
+  <ul>
+     <a name="SQLiteCacheSize"></a>
+     <li><b>SQLiteCacheSize</b>
+     <ul>
+       <code>
+       attr &lt;device&gt; SQLiteCacheSize &lt;Anzahl Memory Pages für Cache&gt;
+       </code><br>
+
+       Standardmäßig werden ca. 4MB RAM für Caching verwendet (page_size=1024bytes, cache_size=4000).<br>
+       Bei Embedded Devices mit wenig RAM genügen auch 1000 Pages - zu Lasten der Performance.
+     </ul>
+     </li>
+  </ul>
+  <br>
+
+  <ul>
+     <a name="SQLiteJournalMode"></a>
+     <li><b>SQLiteJournalMode</b>
+     <ul>
+       <code>
+       attr &lt;device&gt; SQLiteJournalMode [WAL|off]
+       </code><br>
+
+       Moderne SQLite Datenbanken werden mit einem Write-Ahead-Log (<b>WAL</b>) geöffnet, was optimale Datenintegrität
+       und gute Performance gewährleistet.<br>
+       Allerdings benötigt WAL zusätzlich ungefähr den gleichen Festplattenplatz wie die eigentliche Datenbank. Bei knappem
+       Festplattenplatz (z.B. eine RAM Disk in Embedded Devices) kann das Journal deaktiviert werden (<b>off</b>).
+       Im Falle eines Datenfehlers kann die Datenbank aber wahrscheinlich nicht repariert werden, und muss neu erstellt
+       werden!
+     </ul>
+     </li>
+  </ul>
+  <br>
+
   <ul>
     <a name="syncEvents"></a>
     <li><b>syncEvents</b>