Version 1.3.174.
Change of COLLATION influences how strings are checked for equality.
SET COLLATION en STRENGTH PRIMARY;
CREATE TABLE TBL_IGN_CASE ( STR VARCHAR(100) PRIMARY KEY );
INSERT INTO TBL_IGN_CASE ( STR ) VALUES ('E-12345');
INSERT INTO TBL_IGN_CASE ( STR ) VALUES ('E12345');
> Unique i
> What settings can be used to reduce the amount of time to recover after
> reboot (smaller transaction log, etc)?
Try to issue 'CHECKPOINT' just after 'CREATE INDEX'. That helped me.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to th
> dboptions=;CACHE_SIZE=262144;DB_CLOSE_ON_EXIT=FALSE;LOG=1;WRITE_DELAY=3000;
> MVCC=TRUE
> Any thoughts?
Try removing "LOG=1;WRITE_DELAY=3000;"
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to h2-database@go
ENT.
>
> Thanks a lot.
> Viji
>
> On Dec 7, 6:01 am, Noel Grandin wrote:
>
>
>
>
>
>
>
> > That sounds like a reasonable suggestion to me.
> > (not that I'm volunteering to implement it, little busy on another
> > open-source project right now).
> - when run in memory - 1500ms
> - when not run in memory - 426ms
Due to Garbage Collector? Try setting -Xmx high enough to hold all
that data in memory.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to h
presure on a network
if the DB is placed on NFS volume (or ZFS on SAN). I'm talking about
the current implementation of Database.createTempFile(). A parameter
to set a directory for tmp files would reduce remote IO on big inserts/
updates/selects.
On Dec 4, 4:16 pm, Viji wrote:
> Hi Andrei
> Is it related to IO on the local machine. "What is meant is Bad file> number".
http://docs.oracle.com/cd/E19455-01/806-1075/msgs-1050/index.html
"Either a file descriptor refers to no open file,
or a read(2)--or a write(2)--request is made to a file that is open
only for writing or reading."
> How can I truncate the log without starting the database over from> scratch?
CHECKPOINT http://www.h2database.com/html/grammar.html#checkpoint and
probably http://www.h2database.com/html/grammar.html#set_max_log_size
At least in my case, when time to create an index is about 50sec and
every index
> As Noel suggest, you could split the table in two: one only contains the
> columns that are used a lot, and the other table for the remaining columns.
Yes, I've thought about that solution. I even thought about
possibility to store the data as one-columnt-per-table. But I'm not
sure about perfo
a 32-bit VM, I don't think you're going to get much more than a 2G heap
> on windows.
> Switching to a 64-bit VM and allocating more memory to the virtual machine
> should fix your problem.
>
>
>
>
>
>
>
> andreis wrote:
> > Hi,
>
> > we h
Hi,
we have a database with one table, 800'000 rows, about 50 columns and
one index per column. We currently have a problem with the time it
takes to create all indexes - about 10min. The database size when all
indexes created is about 1.5Gb. We've profiled our application with
jvisualvm profiler
11 matches
Mail list logo
