What is the node table?

[nwind]

I am now two days into step 8 of upgrading from 4.2.2 to 5.1.4 and have been on Step 8 for 40 hours. It seems to still be working, though it has to be restarted a lot. I am approaching 200 million records updated to the node table. What is the node table? Watching this for so long has made me curious. This is new in the 5.0 database. Is it going to make my database a lot bigger or will it be more efficient? Where the heck are 200 million records coming from (800MB database originally)? What comprises a record? I have a hard time believing 200 million records in my database, but then, I don't know what exactly a record is to this upgrade. Finally, will I live long enough to see this upgrade completed? Step 8 just seems to go on and on. Wish I had shell access!

[Wayne Luke]

The node table is the table that contains all the content of your site.

The number isn't the number of records actually. It is the number of record IDs in your old table. If you deleted content or ran multiple imports over the years, you can have large gaps in these record IDs and we still have to look at every one.

However there are many "Step 8" steps in going through 4.2.2 to 5.1.4. If you provide more information, like a full screen shot with details open and the name of the script in your address bar, we can provide more help.

[nwind]

Here is my screen shot. I did prune nearly half of my database because it was too big to move. I did all the rebuilds except the counters and ran several optimization/repairs. I was then able to upgrade to 4.2.2 and redid the rebuilds and repair/optimizations. This has been going on since about 4:00 pm Wednesday.

[Zachery]

If there is a lot of data, you need to let it get processed.

[nwind]

It does still seem to be working, but I can't imagine how long we are going to be down. Still, I did play around a bit with version 5 before it had my data, and I am quite impressed with all the improvements over 4.0.

[Mark.B]

Huge sites can take hours, even days, to process all the data. There's no means to speed this up.

[nwind]

Just an update: It's Sunday morning and we are still processing records, approaching 400,000,000. I can't imagine what this would be if had not had to prune over half my database to move it to the new server!

[Wayne Luke]

It is caused by large empty blocks in your table IDs. Most of it is probably empty but they still need to be processed. So you have a post ID 1 and the next one is 250,000. It still has to process everything between 2 and 249,999. Not really any support we can give for this in the forums. If you really think it is a problem, you need to open a support ticket and provide complete access to your server. SSH, SFTP, AdminCP, and Database.

[EdQ]

Trying this on my test site. It has been days....and still running.
Before I upgrade my production site, it there anything I can do to the DB??

[Wayne Luke]

Run the upgrade from your server's command line. It will go faster as the overhead and timeouts associated with a web display are eliminated.

[EdQ]

Thanks....much faster