Sorry, I really missed the boat on supplying information.

> How about starting this triage by telling us
> 1. Which server version

Firebird 1.5.2.4731

> 2. Which model (superserver/classic)

Tried both, but currently superserver

> 3. Which OS and hardware platform (includling CPU setup)

Windows 2003 Web Edition (all windows updates up-to-date), Dual Xeon
2.8GHz with HT turned off, 2.0GB RAM & 3 SCSI drives in RAID 5. So
when I said it used up 100% before, I meant of one of the processors.

> 4. Whether hyperthreading is active on the server host

Hyperthreading is off.

> 5. What you are using for the application environment

The applications are running on a seperate server that is identical to
the one the database is on. The applications are written in ColdFusion
, connecting through ODBC, and ASP.NET, connecting through Firebird
.NET data provider.

> 6. Which platform the apps are running on

Not sure if I answered this anwer in the previous one, if not can you
please explain what you are looking for.

> 7. Whether the client library versions match the server version

Yes

> And show us the output of gstat -h.taken when the performance seems

to slow down.

Database header page information:
Flags 0
Checksum 12345
Generation 4049
Page size 8192
ODS version 10.1
Oldest transaction 3806
Oldest active 3807
Oldest snapshot 176
Next transaction 4042
Bumped transaction 1
Sequence number 0
Next attachment ID 0
Implementation ID 16
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 3
Creation date Dec 14, 2005 23:35:08
Attributes force write

Variable header data:
Sweep interval: 2000

> Also say whether you are using the -g switch for your backup and

whether you are restoring with gbak -r or gbak -c.

I did not use the -g switch for my backup. I used the -c switch and
transfered the alias to the new database.

Early this morning after we tried archiving a lot of the data, we got
the database file down to just over 1gb. It was still slow, so we
moved it to the server the applications are on. The performance seems
back in line with what we were used to; however, I can not keep it on
this server because the load gets to high and overall performance will
dip. So, that leads me to believe that it has something to do with
slow access times to the hard drives. I did some diagnostics on the
hard drives and nothing came up unusual. Maybe something else is the
bottleneck? Any ideas or input would be greatly appreciated.