Large gap is not caused by lack of auto sweep. It is bad system design.
As you is not the system programmer, you can shut down all connections to the
database during lunch time, then you can let users enter in your system again.
After shutting down, run a manual sweep (gfix –sweep). If you see a
what I'm doing right now. Its the only way to keep them going.
I shut them down at lunch, run a sweep, then when they get back in, things are
much faster.
-Josh
On Tue, May 13, 2014 at 8:35 AM, 'Fabiano - Desenvolvimento SCI'
fabi...@sci10.com.br [firebird-support]
wrote:
Your problem is:
"PLAN JOIN (SP NATURAL, A INDEX (ADVOCATE_))"
Wish means a full table scan on SUPPROG. It is strange, because you have the
index
USV_SUPPROG_ADVOCATE_CODE ON field ADVOCATE_CODE
Try this:
select * from
(
select a.User_ID
from Advocate
where a.USER_ID=37
) as FI
Maybe.
Try update all index statistics. MAYBE it helps.
In last case MAYBE a backup/restore can help too… (or drop and recreate those
indexes)
De: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Enviada em: terça-feira, 13 de maio de 2014 17:15
Para: firebird-supp
We also shutdown our database using gfix. We never have a database corruption
because this.
BUT we do not kill any fb_inet_server.exe instance. For us, gfix always be
enough to shutdown all active users – even when using IBExpert.
De: firebird-support@yahoogroups.com [mailto:firebird-supp
Maybe you dont have a HDD cached controller.
Run a program like Crystal Disk Mark in the old computer and in the new
computer. If the performance of new computer is terrible you must change your
physical hard disk controller.
I had this problem with a Dell server that is a “internet server” (w
Maybe this can help:
SELECT st.mon$statement_id as "Statement ID",
st.mon$attachment_id as "Attachment ID",
st.mon$transaction_id "Transaction ID",
case
when st.mon$state = 0 then 'IDLE'
when st.mon$state = 1 then 'ACTIVE'
end as "State",
FB
De: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Enviada em: segunda-feira, 18 de agosto de 2014 16:47
Para: firebird-support@yahoogroups.com
Assunto: Re: [firebird-support] object is in use
Hello Carlos.
Thanks.
I am using IBExpert to run an 'CREATE
Also, FB 2.5.0 has problems with this. If you use this version upgrade to
2.5.1 or above.
De: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Enviada em: segunda-feira, 18 de agosto de 2014 16:47
Para: firebird-support@yahoogroups.com
Assunto: Re: [firebird-support]
You can create a computed index for this:
CREATE INDEX idxname ON mytable COMPUTED BY (lowercase(mymemo))
Hope this help you.
De: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com]
Enviada em: sexta-feira, 5 de setembro de 2014 08:51
Para: firebird-support@yahoogro
Ann, about the third problem:
“The third problem is two records in a referencing table lack mates in the
referenced table, despite a referential constraint. I have no idea how that
happened, but it should be reasonably easy to fix in your database.
”
I saw this happen two times, it is relate
It is a good idea to backup and restore the database to recreate them with the
new OSD.
This will improve performance and MAYBE this can solve your problem.
De: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Enviada em: quarta-feira, 29 de outubro de 2014 11:05
Pa
12 matches
Mail list logo