LN: TSMP has gone from Version 2.1 to Version 3.0. Does this mean that TSMP 3.0 is something substantially different from Version 2?
CW: It does. Both TSMP and CMM have undergone some radical restructuring work. The project goal was to target the product on to a large scale Database Management System - moving away from the Access file based system. Currently we are looking at Microsoft SQL Server and Oracle. Another important change is that we have integrated a lot of CMM/TSMP common code.
LN: The major change in version 3.0 is the switch away from an Access based system; what are the key benefits of the MS SQL Server/Oracle platform?
CW: The key benefits for us, and our clients, are Robustness and Security. In addition, performance on "number crunching tasks" is improved. There are also benefits from the improved Transaction Management that a DBMS offers. We can also take advantage of the server based environment. Let me give you an example, An MI (Management Information) Period report used to take 30 minutes or so on our development environment, the same report against the same data now takes a couple of seconds.
LN: That is a pretty impressive increase; is it simply accounted for by the different platform?
CW: No. A major advantage of running on a "back end" database is that the DBMS is operational for 24 hours a day. We can make use of this, as in the example above, by doing many common calculations once for the database. These would have previouly been done every time the report was run, on the client PC. This data summarisation can be run overnight on the server. This means the user gets the report very quickly.
If we look at example where we are not using the summary data, for instance, the "Contract performance by Product Report". In a reasonably large database this used to take nine minutes, this report now takes 17 seconds.
For other tasks, which don't involve number crunching or manipulation of large data sets, such as form filling, performance is about the same - governed by the speed of the client PC.
LN: Aside from the major architectural changes, are there any functional changes?
CW: Only a few - mainly to do with locking issues and a few other changes for the environment. Bugs have been fixed of course, and other "loose ends" have been tidied up. The intention of the port was to move the existing system, and get that stable and working well before making any functional changes. When 3.0 is proven then the functionality will be altered, for example 97/98 changes. We have made some minor changes, for example, we've moved the Finish button to the Menu Bar to make it harder to accidently exit the application at the wrong point. We've also improved the layout when running on SVGA screens.
LN: So the User Interface is the same?
CW: Yes, we're still using Access 2.0 - using it as a client. The access database stores only the client code, forms and so on. There is a complete separation between the data, the processing of the data and the client which provides the User Interface. This is a true Client Server system. Of course, the client software will need to be updated, but we've been working on a setup program to automate this process as much as possible. It's very nice actually.
LN: So are there any re-training issues?
CW: Not for the end user, however, the Systems Adminstrator will need some - we shall be running a suitable training course from February.
LN: Microsoft SQL Server runs only on the Windows NT Platform. Is this only platform you are targetting?
CW: In the main, however we expect the Oracle version to be used on both NT and Netware servers. The requirements for an NT server are for a system with around 500MB of disk space, for SQL server and the databases and transaction logs. You'll need at least 32MB of memory, the more the better. In terms of CPU, a Pentium 133 or better would be needed. For the NT environments we are looking at both Intel and Digital Alpha (AXP) servers.
LN: Is Windows 95 for the client supported?
CW: Good Question. Windows for Workgroups 3.11, Windows 95 and NT Workstation 3.51, 4.0 are supported. There are benefits to be gained from the 32 bit operating system (95 and NT) as this allows 32 bit ODBC drivers to be used. This enables trusted connections which reduce the number of log-ons required. The client environment is still the 16 bit Access 2.0 one, so it will run fine on the 16 bit operating systems.
LN: What other benefits are there?
The other benefits fall into a number of areas:
Firstly, support. We anticipate that the new environment will make product support easier in a number of ways. We will now be able to access the customer system via dial in connections "live" - while dealing with the support call. This will lead to swifter problem diagnosis and resolution. Also, many problems associated with the Access Environment will no longer apply.
For development, the restructuring of the source code means that future developments will be quicker. We can also use some other development tools which create a more controlled, and therefore, more reliable and efficient development environment.
The system is now much more open. The advanced user, using GQL or some other direct query interface will benefit greatly from the aggregated information. This is the summary information calculated overnight. This information is the basis for many of the adhoc queries which are made. The users will be able to get answers to these questions more quickly.
For the administrator there are benefits too. The DBMS tools for administering the database, performing backups and so on should make life easier.
LN: What are the project timescales now?
CW: We are currently completing alpha testing now [January]. Implementation and beta testing at Suffolk TEC will start at the beginning of Feburary.
LN: What are the Future Plans?
We have the 97/98 changes in the pipeline. There are a few other things coming along which I think are exciting..
LN: But your not going to say anything about them yet?
CW: No - not yet, watch this space...
LN: Thanks for your time Chris.