C
ChUIMonster
Guest
No. It is not "safer" to do all of these things "just in case". You need to understand which of these possible options are actually needed for your particular situation. You probably do not need all of them. Depending on what you are doing and why some of them can actively damage the success of a dump & load. In particular dumping all hidden files is almost always a bad idea. Dumping selected hidden files that a specific application requires *might* be necessary -- but it might also be problematic. When an application uses hidden files the designer is probably implementing some sort of licensing or copy protection schema and there is a good chance that you need to work with the supplier of that application to successfully manage the creation of a new instance of the db.
Continue reading...
Continue reading...