Re: A thought on re-indexing of a large database after repairs, compacting etc

Chuck, You know the old saying: “A watched pot never boils.” Watching 4D reload the same table with 7 million records 8 times to generate 8 indexes is kind of like that. I don’t have the luxury of installing an SSD RAID. I’m sure better hardware would help. Paul > Le 23 avr. 2018 à

Re: A thought on re-indexing of a large database after repairs, compacting etc

OK I don;t get it. We have a data base of over 200 Gig with many millions of records. We run using SSD,s in an Areca RAID. 1 Terabyte SSDs. I can tell you that when we restored from a backup up and rebuilt indices it took not more than 20 minutes to so. It does not matter if it is by table or

Re: 4d servers down

We can't access it either:-( Very unstable recently. Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >livedoc, taow, 4dbb web servers do not respond. >So do you? > >-- >Arnaud de Montard > > > >** >4D Internet

4d servers down

livedoc, taow, 4dbb web servers do not respond. So do you? -- Arnaud de Montard ** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options:

Re: v13+ LEP permision issues.

thanks Jim, I think I did that, but I will try again. > On Apr 20, 2018, at 5:45 PM, Chip Scheide via 4D_Tech > <4d_tech@lists.4d.com> wrote: > >> Trying to rename a file. > [snip] >> when I execute the below line of (LEP) code I get a permissions error >> mv /Volumes/Macintosh\

Re: v13+ LEP permision issues.

On Apr 20, 2018, at 5:45 PM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> wrote: > Trying to rename a file. [snip] > when I execute the below line of (LEP) code I get a permissions error > mv /Volumes/Macintosh\ HD/Users/chip/Desktop/_Test\ File\ > move/Some_Win_Name.txt2 Testing.txt > >

Re: A thought on re-indexing of a large database after repairs, compacting etc

> Le 22 avr. 2018 à 11:08, Paul Lovejoy via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > Hi, > > I guess our database of 120gb, running on a 32 bit machine doesn’t benefit > from this. We were working on the most recent R release and yesterday we went > to 15.5. > When reindexing the

Re: v13+ LEP permision issues.

f.y.i. https://github.com/miyako/4d-plugin-rename 2018/04/21 7:42、Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> のメール： (rename a folder for example) ** 4D Internet Users Group (4D iNUG) FAQ:

Re: A thought on re-indexing of a large database after repairs, compacting etc

15.5 maybe a newer release than 15Rx, but it is an older branch. 15.0 ➡︎ 15.1 ➡︎ 15.2 ➡︎ 15.3 ➡︎ 15.4 ➡︎ 15.5 ┗15R2 ┗15R3 ┗15R4 ┗15R5 ┗16.0 ➡︎ 16.1 ➡︎ 16.2 ➡︎ 16.2 left to right: bug fixes top to bottom: new features 2018/04/22 18:08、Paul Lovejoy via 4D_Tech

Re: A thought on re-indexing of a large database after repairs, compacting etc

Hi, I guess our database of 120gb, running on a 32 bit machine doesn’t benefit from this. We were working on the most recent R release and yesterday we went to 15.5. When reindexing the entire database, 4D Server/4D are still going index by index instead of table by table. Or maybe I missed

Re: A thought on re-indexing of a large database after repairs, compacting etc

Hi Jeff, We are on 15.5 now. I don’t see any R releases which are more recent. v15.5 does not do this… Paul > Le 21 avr. 2018 à 17:06, Jeffrey Kain via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > 4D implemented this very improvement in the v15 R releases. > > -- > Jeffrey Kain >