Database repair question

[okhiu]

Hello, i have a question regarding database repair process.

Why when i do the database repair, at the "scanning for deleted asset files" step it shows me also the download station items? And the same at the "Scanning for modified asset files" step. I get 206,826 items to be scanned, and for about 68.5 GB of content i wait approximately 3 hours.

But, a friend of mine, who does not have an original copy of Trainz, he waits only 40 minutes for 48.5 GB. And he gets only about 40,000 objects to be scanned, which are only the items installed by him. Why does my game show all the items (i definetly don't have 200k ) and is there anything to be done to fix this? I tried to remove my username and password from the Options menu but it is not working. Any other ideas?

Thank you.

 

[WindWalkr]

Why when i do the database repair, at the "scanning for deleted asset files" step it shows me also the download station items? And the same at the "Scanning for modified asset files" step. I get 206,826 items to be scanned,

...

Why does my game show all the items (i definetly don't have 200k ) and is there anything to be done to fix this?

It's working as it should, so you don't need to "fix" anything. The presence of DLS items in the database won't slow anything down or cause any problems. It just means that your install knows of the existence of those items on the DLS.

kind regards,

chris

 

[okhiu]

It's working as it should, so you don't need to "fix" anything. The presence of DLS items in the database won't slow anything down or cause any problems. It just means that your install knows of the existence of those items on the DLS.

kind regards,

chris

Ok but why do i have to wait 3 hours for 68.5GB and my friend is waiting 40 minutes for 40GB? I mean i wait 4 times longer than he does, but i only have 60% more content than him...So if i do the math...i should wait 1h+ not 3h+

 

[shaneturner12]

The longest point in the majority of database repairs is the 'checking for faulty assets' stage.

It may well be that TrainzUtil cannot process items as quickly.

Shane

 

[Kon1786]

it can be a long wait, every so often ill run it before bed and when i wake up its done and my trainz runs much better,,,

 

[okhiu]

It seems that my guess was right

After a fresh TS installation, i havent entered my Auran account, and there you go

The database repair does not include in the check also the DLS items. Those 29002 items are only the items installed by me.

Will get back and let you know how much it took to repair.

Later edit: It took about 1 hour to fix those items, so i hope when i will install all the content will take 2 hours maximum if database repair is needed...not 4 or 5 like it did before...

 

[WindWalkr]

Ok but why do i have to wait 3 hours for 68.5GB and my friend is waiting 40 minutes for 40GB? I mean i wait 4 times longer than he does, but i only have 60% more content than him...So if i do the math...i should wait 1h+ not 3h+

Either your computer is slower; the content that you have is more complex; or you're wrong about how much more non-built-in content you have installed compared to your friend.

kind regards,

chris

 

[JCitron]

A highly fragmented hard drive will make your database repair process take a much longer time.

Try running a defragmenting utility on your hard drive prior to running Trainz or doing a DB repair. You'll see a nice improvement in data operations.

Konan:

it can be a long wait, every so often ill run it before bed and when i wake up its done and my trainz runs much better,,,

I noticed this too. I wonder if the process also compresses any extra dead space and does some reindexing as well as well when going through the repair process.

John

 

[okhiu]

Yes, you are right, defrag helped a lot, but what i wanted to underline here was that it seems if the DLS items are included in the database repair process analysis, this process takes much much longer.

 

[clam1952]

Yes, you are right, defrag helped a lot, but what i wanted to underline here was that it seems if the DLS items are included in the database repair process analysis, this process takes much much longer.

It is physically impossible for Content manager to check and repair items on the DLS that are not on your PC, the amount of files would around 200,000 plus and you would be there for a couple of days while it checked them all. You are seemingly not understanding what happens.

There are people who take longer to run a 40 GB database repair than your friend, takes 3 or 4 hours here on a low spec PC and 45 minutes on a high spec one for the same size. Makes no difference if the PC's are on or off line.

Computers are all different, even identical spec machines can perform differently. Just because Computer A does something in X amount of time doesn't mean that Computer B is capable of doing the same.

Consider the various Operating system types, speed of proccessor, number of cores, type and speed of hard Drives, free space, type and speed of memory and what other tasks and programs are running while you are performing a task.
All will affect the time taken, Databases by their nature are large and take time to sort.
Backup and repair functions in commercial situations are done out of work hours where possible because of the time taken.

 

[shaneturner12]

A slight correction...

It does in fact check the DLS items (the ones Content Manager knows about via the caching processes) during a database repair, but it does not perform fault checks on them - it simply checks that the information held about them is correct (it checks them in the deleted,added and modified stages).

The reason I know that is that I've checked how many assets I have locally installed, and it's between 10 and 20 thousand. The database repair though checks about 180,000 or so.

The remainder is the Download Station assets.

Shane

 

[okhiu]

A slight correction...

It does in fact check the DLS items (the ones Content Manager knows about via the caching processes) during a database repair, but it does not perform fault checks on them - it simply checks that the information held about them is correct (it checks them in the deleted,added and modified stages).

The reason I know that is that I've checked how many assets I have locally installed, and it's between 10 and 20 thousand. The database repair though checks about 180,000 or so.

The remainder is the Download Station assets.

Shane

Yeap exactly. If clam1952 would have read my first post, i was saying the same thing there: when i am connected to DLS, during database repair Content Manager reads about 220,000 items, although i only have about 40,000 installed. And it does this counting at all steps of repairing the databse so it does take longer if you are connected to DLS, no matter what some say. I also posted a screen with the items count when not connected to DLS. And if for 40,000 items it takes about 20 minutes to read and scan the deleted asset files and added asset files, you do the math for 220,000 items I'd say its almost 2 hours