when we restore a back up, if the database is not enough in size then restoration would stop, prompting to expand the database and then restore again. Probably many would have observed that if this happens at the point of creating keys, then after we expand the database, system starts from the last key creation where it stopped and continues to restore the database. I wanted to know where this information is stored? Is it stored in the database or in any other files on the disk? i presume is in database.
I Navision backup of data always includes all the table objects, (even if you don’t backup objects). When you start a restore, the first thing that happens, is that these table objects are imported into your Navision database, BUT with different numbers. I can’t remember the exact numbers, but it adds something like 100,000,000 to your existing table. For example the Sales Header might be 100,000,036. It then imports the data into these new tables. Once all the data has been imported, it then moves the data from these new tables, into the real ones. And of course at this point if there are any problems, like a different table definition, or more commonly if there is already a company of the same name, then the import fails. If the move works, then it starts sorting the keys.
Now if you want, you can log into the database with another client whilst you are restoring, and you can see these tables, and get an idea of what is going on. Just make sure that you don’t accidentally create a new company, that could kill the restore mid process. Try it out on Cronus.
I don’t think those tables are still around once the key generation starts. Is it relevant to know where it stores that information? All you need to do is make sure you have enough room in your database file, and make sure that you complete the restore process.