HoleBASE SI – 5 Things You Should Think About Before Migrating
Please note that the following news item is an archived article. Therefore any links and information may now be out of date.
1. Where to put the Network Licence Manager (who do you want to share your licences with?)
HoleBASE SI sees the introduction of a new licensing mechanism that gives the potential of floating licenses anywhere in the world. It’s one of the great benefits of HoleBASE SI over HoleBASE 3.1, we have done away with the hardware locks and the office based restrictions.
Now to use HoleBASE SI your computer just needs to communicate to your Network Licence Manager server, the computer can be anywhere. To do this your computer needs to be on the same network as the licence server, if you working from a different site, you just need a wide area network or VPN. The network link does not need to be fast, it just needs a connection.
If you don’t want to share the HoleBASE SI licences with other sites or offices then just leave the Network Licence Manager on your local network.
Just one thing to remember socket 1947 needs to be open on the firewall for the computers to communicate with the licence server.
For more information on the Network Licence Manager see Chapter 2 of the HoleBASE SI Network Installation Guide which can be downloaded from here
2. Where to put your database server (who do you want to share project data with?)
The consideration here is similar to that of the Network Licence Manager, HoleBASE SI uses SQL Server to store and share data. Who do you want to access this project data? Do you only want people in the local site and office to access it or do you require people from remote offices, even in different countries to access it?
The big consideration here is the speed and quality of the wide area network. HoleBASE SI is designed to work over slower networks, but it will still require a reasonable bandwidth. There are so many different ways to set up IT infrastructure that it is impossible for us to currently estimate how fast it will work on your systems. However it should be quite easy for you to conduct your own tests with a trial version of HoleBASE SI.
If you do not have a satisfactory Wide Area Network, or you just do not wish to share projects between offices, then set up a different database per office.
Also, like the Network Licence Manager, you will need to open up ports and sockets to allow HoleBASE SI desktop to communicate to the SQL Server. Again information on this and other database considerations can be found in Chapter 3 of the HoleBASE SI Network Installation Guide which can be downloaded from here
3. What version of SQL Server do I need? (Can I use the free one?)
Currently HoleBASE SI only works on SQL Server 2008 R2 SP2. However there are many different editions of Server 2008 R2 SP2, HoleBASE SI should work with them all, although a word of warning we have only tested with Express and Standard.
|Number of CPUs||OS maximum||8||4||4||2||1|
|Maximum memory utilised||OS maximum||2 TB||64 GB||64 GB||4 GB||1GB|
|Maximum database size||524 PB||524 PB||524 PB||524 PB||524 PB||10 GB|
|Number of HoleBASE SI projects||unlimited*||unlimited*||unlimited*||unlimited*||unlimited*||250|
SQL Server Express is the free edition and is the ideal platform for companies that have up to 5 licences of HoleBASE SI and are running a system with around 250 projects in it. These are purely estimated figures and you may find that the system will work well using SQL Server Express if you have more licences or more projects.
*One PB (petabyte) = 1 million GB, = 25 million projects, this means the other editions will effectively work with an “unlimited” number of projects.
4. What custom fields and tables need to be created before I import data (can I just bulk import data?)
If you intend to migrate existing HoleBASE 3.1 projects into HoleBASE SI it is essential you conduct an audit of any custom fields or tables you may have used. When old projects are imported into HoleBASE SI, and custom fields are not mapped to the correct location in HoleBASE SI or do not have new appropriate fields created some data may be lost in the migration process.
However care should be taken not to duplicate fields, use the Model Structure command under Configuration in HoleBASE SI to check for an existing field to migrate your data to.
5. What projects do you want to import into HoleBASE SI (Do your borehole have coordinates?)
Finally, what legacy data do you want to import into HoleBASE SI? HoleBASE SI uses the project list and project map to enable you to quickly find and access historic projects. This data may be very valuable in new projects and could give you a competitive advantage. To maximise the benefit, you need to import the data with valid coordinates in a known projection system. Note: it is possible to add locations once the project has been imported.
Thursday 19 October 2017
Monday 24 July 2017
Thursday 20 July 2017