A database created on Starcounter 2.2 is not compatible with Starcounter version 2.3. Thus, an application created on Starcounter 2.2 will have to have its data migrated to work properly.
In Starcounter 2.3 and 2.4 the old
staradmin unload and
staradmin reload commands have been replaced with a new tool - StarDump.
The tool is available from the installation folder starting from
18.104.22.16827 Starcounter versions. By default the StarDump tool is located in
C:\Program Files\Starcounter\stardump folder.
The StarDump tool unloads Starcounter database into an SQLite dump. The dump file can be viewed or modified by any tool compatible with SQLite. The recommended tool is - DB Browser for SQLite.
StarDump.exe unload --database [DatabaseName] --file [FilePath]
StarDump.exe unload --database default --file C:\Temp\default.sqlite3
Before upgrading from 2.2 in order to reload, delete the directory at
\<User>\Documents\Starcounter since it is not compatible with 2.3+. Warning! this will delete all the database files, ensure that it's properly backed up first.
StarDump.exe reload --database [DatabaseName] --file [FilePath]
StarDump.exe reload --database default --file C:\Temp\default.sqlite3
Note: the database should be dropped and created prior to reload.
staradmin -d=default delete --force dbstaradmin -d=default new db DefaultUserHttpPort=8080
The StarDump.Migrator.2.2 app produces an SQLite dump from Starcounter 2.2 database.
Things to know about
It is only compatible with Starcounter 2.2 and won't work with 2.3 or 2.4.
It is a Starcounter app which has to be started the same way as any other apps do.
It is not able to reload database dump, only unload.
All the apps defining
[Database] classes should be started prior to unload with
Start all of the applications which contains classes marked with
The produced SQLite dump is compatible with the StarDump tool and can be used to reload database into Starcounter 2.3 or higher.
During migration from Starcounter 2.3.1 to version 2.3.2 you can experience errors about missmatching schemas. Those are aftermaths of changes in data-model schema that were made during 2.3.1 version development. To fix those errors you can manually run those commands in the administrator SQL command line:
ALTER TABLE Starcounter.HtmlViewAttachment DROP COLUMN AttachedViewUriALTER TABLE Starcounter.HtmlViewComposition DROP COLUMN MainViewUriALTER TABLE Starcounter.HtmlViewComposition DROP COLUMN Version