Question
Microsoft Access database randomly locks itself??!
Hi there
Our Access database is doing something weird. Every so often (I think when we've had a busy day in terms of traffic) a .ldb file randomly appears in the directory where our database file resides. Whilst this .ldb file is in existance the CF application can't read (or write) to the database and thus eventually CF times out and returns an error (or the user's browser gives up and displays a 404 error).
Sometimes this .ldb file dissapears of it's own accord after a second or so, but at other times it doesn't go away again and we have to restart the server.
- not ideal!
does anyone know why this occurs?
I've heard that running a deliberatly bad query (ie selecting from a non-existant table) can 'clear' this .ldb file - in fact we went as so far as to run such a query every 10 mintues as a scheduled task as a preventative measure - and although it 'feels' like this may have helped, we do still get these random .ldb files appearing every now and then and thus we have to restart the server :(
our site is getting busier (450,000 page impressions last month) so maybe we need to migrate to a new database (mySQL perhaps?)
however we don't want to go through all the pain of migrating to another database (is that hard to do?) only to find that wasn't the cause of our problem.
any input would be very gratefully received.
thank you very much.
Our Access database is doing something weird. Every so often (I think when we've had a busy day in terms of traffic) a .ldb file randomly appears in the directory where our database file resides. Whilst this .ldb file is in existance the CF application can't read (or write) to the database and thus eventually CF times out and returns an error (or the user's browser gives up and displays a 404 error).
Sometimes this .ldb file dissapears of it's own accord after a second or so, but at other times it doesn't go away again and we have to restart the server.
- not ideal!
does anyone know why this occurs?
I've heard that running a deliberatly bad query (ie selecting from a non-existant table) can 'clear' this .ldb file - in fact we went as so far as to run such a query every 10 mintues as a scheduled task as a preventative measure - and although it 'feels' like this may have helped, we do still get these random .ldb files appearing every now and then and thus we have to restart the server :(
our site is getting busier (450,000 page impressions last month) so maybe we need to migrate to a new database (mySQL perhaps?)
however we don't want to go through all the pain of migrating to another database (is that hard to do?) only to find that wasn't the cause of our problem.
any input would be very gratefully received.
thank you very much.
AdChoices