I see Michael and Das have provided some responses already, but here’s a bit from me too.
I’m currently working for a company that has exactly the problem you describe – maxed out datafiles. (Actually, it’s an Omnis 7 application, but the theory should be the same for Studio.)
To get away with expanding datafiles for a number of years, they identified the biggest files (i.e. file formats that take up the most space) and moved each of them into its own datafile.
e.g. You can have:
– one datafile with all the standard reference data file formats in it
– one datafile with the Client data in it
– one datafile with the invoice data in it
Each datafile can have 15 segments.
This creates much more space than limiting yourself to one 15-segment datafile for everything.
As your application opens each of the datafiles, the code must say ‘Set default datafile …..’ specifying the file formats that are in that datafile. Then when your code performs an operation on a file format like Find or Insert, Omnis simply uses the correct datafile for the file format concerned.
It’s a good idea to make sure that you have record locking under strict control too – make sure all file formats are in read-only mode until you really want to update a record. When Omnis is locking multiple records across multiple datafiles, it seems you can have more chance of deadlocks or data corruptions.
Please contact me privately or on list if you want some more help on any of this.
DF1 or SQL:
I do not recommend using the Omnis datafiles as a long term solution for large datasets. My team has been hired to migrate the application I describe above to SQL and it’s a significant task. We’ve developed a way to do so that keeps the old code base rather than having to rewrite it all in SQL today. We cleanse various aspects of the application, then pass it through a converter that replaces all the old Omnis DML commands with ‘equivalent’ SQL operations. This might be an approach you want to consider once you’ve got past the immediate space issue.
> On 1 Mar 2018, at 20:25, Jeanne Reyes <email@example.com> wrote:
> I have a native studio database with 15 fully expanded segments totalizing
> (3.75 gb). My understanding is that Studio can handle up to 1 terabyte of
> data, but with only one database is not possible. I think I remember that
> there is a way to link databases together.
> I’m running out of space and can not close the older data until a couple of
> years form now. How can I have several datafiles, but still have them
> treated as one for the purpose of reporting and historical data? and no, I
> cant use SQL (tried, failed, my try again in the future)
> Jeanne Reyes
> Shop online through this
> link to help me pay for college!
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:firstname.lastname@example.org