Being Java programmer.
Being Java programmer.
Roel De Nijs wrote:From a database perspective 3000 inserts each day is pretty low and way beyond the limits of SQLite.
We have used Oracle, PostgreSql and MySql in Production.Ganish Patil wrote:I'll perform 2500 to 3000 inserts operations everyday means within 12 hours and also perform select, update on those records. It is project for retail shop who has employees...
Roel De Nijs wrote:Other alternatives are H2, HSQLDB, and Apache Derby. And here you'll find a comparison of different popular embedded (lightweight) java databases.
No more Blub for me, thank you, Vicar.
Ron McLeod wrote:
Roel De Nijs wrote:From a database perspective 3000 inserts each day is pretty low and way beyond the limits of SQLite.
Did you mean way below rather than way beyond?
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Being Java programmer.
Being Java programmer.
Being Java programmer.
do you really want to be searching through transactions from 5 years ago when you only need to see yesterday's?
Being Java programmer.
Being Java programmer.
Being Java programmer.
Bear Bibeault wrote:2500 records is a ridiculously small number of records that any database will be able to handle.
Ganish Patil wrote:@ chris webster
do you really want to be searching through transactions from 5 years ago when you only need to see yesterday's?
No, (Assume application has records of year 2011 to 2015 ) If I want to calculate the total products delivered to a customer in a month of 2015 then It should not start searching from records of that customer of year 2011 to year 2015, rather It should start searching directly from year 2015 records. Do I need to use Index here ? If yes then, should I use Index on delivery date or customer Id ? I've never used Index before.
Tapas Chand wrote:NOTE: Bad index can horribly lower the performance of database.
Being Java programmer.
Dave Tolls wrote:I don't think I've seen that (unless the index stats are seriously out of date, but that's a DBA issue). If the stats are up to date, then the generated plan should not use the index if it's worse than a full table scan.
Tapas Chand wrote:Bad index will not affect performance of SELECT queries, but it will definitely affect performance of DMLs, because for each DML, database has to touch each index of that TABLE.
And sometimes it can really lead to a deadlock.
Dave Tolls wrote:I will say, a DML will only update an index if it involves a change to a column that forms part of that index. Obviously this is the case with any INSERT or DELETE, but not necessarily an UPDATE.
Ganish Patil wrote:This is the table membersales_records structure and it's link link of table structure image
Being Java programmer.