Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 5 of 5 total |
Migrating database DBISAM Version 4.26 Build 1 to DBISAM Version 4.44 Build 3 |
Wed, Apr 25 2018 4:40 PM | Permanent Link |
Mesotech Mesotech | Hello,
I've got an old database build with DBISAM Version 4.26 Build 1 version... I use DBISAM Version 4.44 Build 3. Is it necessary to use UpgradeTable property or not ? Can I use directly the database with the last version of DBisam, or I need to backup it and restore it ? With best regards, Mesotech |
Wed, Apr 25 2018 9:04 PM | Permanent Link |
Raul Team Elevate | On 4/25/2018 4:40 PM, Mesotech wrote:
> I've got an old database build with DBISAM Version 4.26 Build 1 version... > > I use DBISAM Version 4.44 Build 3. Is it necessary to use UpgradeTable property or not ? > Can I use directly the database with the last version of DBisam, or I need to backup it and restore it ? > You do not need to run upgrade table (this is more for dbisam 3 to 4 migration). However you should review release notes and make note of warnings (red text ) as well as any breaking changes (notes are available from download page and also installed with dbisam). Main change to consider is blob handling in 2.28 so make sure you do not mix older and newer dbisam versions with same tables. Raul |
Thu, Apr 26 2018 3:23 AM | Permanent Link |
Mesotech Mesotech | Hello,
I read this for 4.28 : " There is a new design for the BLOB reading/writing that is not compatible with 4.27 or earlier. Therefore, it is extremely important that you do not mix DBISAM 4.28 applications with DBISAM 4.27 or earlier applications. Mixing the two versions can cause improper truncation of BLOB data, and that includes using a 4.27 application on any data that has been updated by DBISAM 4.28, even if it is not concurrently. The issue is that 4.27 and earlier versions recycle BLOB blocks on a per-block basis, whereas 4.28 and higher versions recycle BLOB blocks on a per-row basis." If now I change all applications to 4.44, I have some some thing to do do about my old database that was build with 4.26 ? Can I use directly this database without doing anything... (I won't mix application with 4.26 and other with 4.44... All will be now build with 4.44...) With Best Regards, Mesotech |
Thu, Apr 26 2018 4:44 PM | Permanent Link |
Raul Team Elevate | On 4/26/2018 3:23 AM, Mesotech wrote:
> If now I change all applications to 4.44, I have some some thing to do do about my old database that was build with 4.26 ? Can I use directly this database without doing anything... (I won't mix application with 4.26 and other with 4.44... All will be now build with 4.44...) AFAIK you can use it "as is" - newer 4.44 engine will be using the new blob logic on tables once you start making changes (add/delete/modify records). i personally would run VerifyTable/RepairTable at least once after you switch to new engine to make sure all tables and structures are OK to being with. Raul |
Fri, Apr 27 2018 10:20 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Sorry for missing your posts, but Raul has you covered pretty well. Just a quick note: there is a 4.45 update coming soon, and it will entail some other changes that might want to make you hold off on deploying 4.44 into production. Most importantly, 4.45 removes the TDBISAMEngine.LargeFileSupport property, and large file support is *always* on in 4.45 and higher. Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |