There could be significant improvement in the redesign of the Access table. Right now, Scott has only one table which is very flat (in other words, it holds all the data and the data is all ASCII) so if it was designed in at least the 2nd Norm, things would start to move faster. You can help move things along by adding some indexes on some of the tables, such as the callsign field.
toggle quoted messageShow quoted text
There are other things that could be done.
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Jim Shorney
Sent: Monday, November 25, 2019 21:16 PM
Subject: Re: [N3FJPSoftwareUsers] Log too big?
All good points Mike. I was aiming at the lowest common denominator here, the ham that is not very computer savvy and just wants to make'ergofaster. The easiest answer there is to just get a bleeding edge computer. Any current front-line gaming rig should do.
On Mon, 25 Nov 2019 06:21:46 -0700
"Mike Olbrisch" <firstname.lastname@example.org> wrote:
There is more to it than just the volume of records. Amount of memory, amount of FREE memory, processor and speed, and what other programs running in the background can all make a huge difference.
One FREE thing you can do to speed it up is this. Open your task manager and see what-all you have running. Look to see what processes might be monopolizing your processor cycles, or reserving your memory. Turn off those things you don t need.
Look at my QRZ profile-photo of the operating desk. That is an older Win-7 (64 bit) I got from an SK sale. It isn t anything special. The only thing I did was double the memory and clean out all the programs it wouldn t need. All I use it for is logging and digital work. Sure, a nice new Win-10 box would be nicer. But this works, and I see no need to spend $$$$ for a replacement.
If I have to upgrade it from Win-7 to Win-10, it may suffer and need to be replaced once Win-7 is no longer supported. We ll see.
Give it a look. Best of luck!
Mike KD5KC -- El Paso -- Texas.
The canyons are calling, colorful and deep. But I have promises to keep.
And miles to go still in my Jeep... And miles to go still in my Jeep...
ADVENTURE: The respectful pursuit of trouble.
On Sun, Nov 24, 2019 at 6:36 PM Jim Shorney <email@example.com <mailto:firstname.lastname@example.org> > wrote:
27,000 QSOs will slow the database down. That's just the way it is. You can either run in Last 50 mode like most of us probably do or you can buy the fastest bad-boy computer you can get your hands on and equip it with the most RAM and fastest SSD you can get.
On Sun, 24 Nov 2019 15:49:25 -0600
"Dale Martin" <email@example.com <mailto:firstname.lastname@example.org> > wrote:
Any suggestions other than just using the logsheet in the 'Last 50' mode?
There's a lot of 'downtime' in FT8, so I use it to go through the
log and update the not-yet-confirmed QSOs S/R status to Y/Y and
removing the confirmed QSO from LOTW.