Ok, this is pretty weird IMHO. I have some Perl code written to create and populate a SQLite database. It's very simple - a list of users and their AD groups in two different tables. It's been running ok for at least 18 months. I have some other Perl code that will query the database. This querying code has started running slowly, and in some cases returns no results where I know there are records - I can test it by pasting the SQL in to the SQLiteStudio v2.1.5 editor. It returns the results instantly.

Here's an example of some Perl query code:

#!/usr/bin/perl -w
use strict;
use DBI;

my $dbfile = 'C:/db/employee.db';
my $dbh    = DBI->connect(
    "dbi:SQLite:dbname=$dbfile",
    "", "",
    {
        RaiseError        => 1,
        AutoCommit        => 0,
    }
);

my $sql = q{
    select e.*
    from   employees e,
           groups g
    where  e.sam_account_name = g.sam_account_name
    and    g.group_name = 'Group Name'
    order by last_name, first_name
};

foreach my $emp (@{$dbh->selectall_arrayref($sql, {Slice => {}})}) {
    printf(
        "\t\t%-15s %-15s: (%s)\n",
        $emp->{first_name},
        $emp->{last_name},
        $emp->{sam_account_name},
    );
}

$dbh->rollback;
[download]

The query in $sql is copied and pasted into the SQLiteStudio editor. Regardless of the group name I choose, the editor returns rows in approximately 0.001 seconds. Perl takes several seconds may return no rows, even where there are matching candidates. If I change the group name, it may return the same rows as the editor but it can take 10+ seconds. The result set is always small 2 - 20 rows depending on the group. The database is 520MB.

Note the code above was written to simplify my problem. The actual code has the group name as a placeholder, and I simply fetch each row rather than returning everything into an array as I do above. Regardless, the results are the same.

This is running on Windows 7. I was using DBD::SQLite 1.54 - As a test this morning I upgraded to 1.55_04 to see if there were any fixes in the developer version. I recreated the database, but the results are still the same