Since SQLITE 3.7.x there are performance problems

We used EXPLAIN QUERY PLAN and detected differences between machines.

Matthias found out that faster machines (DRAM server) use the "ranges_index"
for the "Transactions" table. But other machines (our laptops) use the primary
key defined for that table. Removing the primary key the performance issues
were solved.

DRAMSys/simulator/resources/scripts/createTraceDB.sql

@@ -48,8 +48,8 @@ CREATE VIRTUAL TABLE ranges USING rtree(
 );
 
 CREATE TABLE Transactions(
-        ID INTEGER PRIMARY KEY,
-        Range   INTEGER, 
+        ID INTEGER,
+        Range INTEGER, 
         Address INTEGER,
         Burstlength INTEGER,
         TThread INTEGER,