| 1. |
What are the biggest advantages that Data Slicer offers application developers?
There are two major benefits for developers using the Data Slicer shared test data environment; 1) Everyone can load test data, run tests, and reload test data within the same DB2 test environment, and 2) New test data instances (test beds) can be built in minutes instead of days or even weeks.
|
| 2. |
What are the biggest advantages that Data Slicer offers DB2 DBAs?
There are two major benefits for Database Administrators using Data Slicer; 1) Replicated DB2 test beds and the huge amounts of work managing them can be eliminated, and 2) Replicated CICS test regions can be reduced freeing up large amounts of CPU resources that might otherwise lead to CPU upgrades due to poor test CPU performance.
|
| 3. |
How long does it take to install Data Slicer? How long does it take to deploy?
Data Slicer only take 2-3 hours to install at your shop. The install is done by a DB2 DBA. It is not an SMP/E install, so no system programmer is required during the process. Deploying Data Slicer is also very, very fast. Building a new shared test bed and then altering it with the Data Slicer Power Slicer Utility takes another 2 or 3 hours. Developers can then start performing side by side tests in old test beds and the new shared Data Slicer test bed to confirm testing results are identical. From installation to a proof of concept of Data Slicer is typically a day or two timeframe at the most.
|
| 4. |
Can we see an online demo of SoftBase Data Slicer?
Data Slicer is an adapter that sits on top of current test data subsetting solutions such as Princeton Move for DB2™ and Compuware File-aid/RDX™. Data Slicer is designed to manage a test data sharing environment and provide data access to each programmer and tester who has placed test data there. While there is an online interface for advanced functionality found in Data Slicer (such as test data library management), SoftBase would prefer to present this component after a proof of concept project has actually been started. The very first step in understanding and deploying Data Slicer is to implement a shared test bed at the customer site.
|
| 5. |
How long is the typical trial of Data Slicer?
Data Slicer does not really require a true software trial and evaluation. Unlike comparisons of large test data subsetting solutions, Data Slicer does not need to have hundreds of features compared against a competitor. Data Slicer is the only product of its kind and can be installed in one morning. Constructing the new shared test bed and then executing side-by-side tests on old and new test beds take a few more hours. SoftBase refers to this process as a "Proof of Concept". This entire initiative usually takes 1 or 2 days at the most. Also, SoftBase would like to provide you with onsite support during this process which will ensure that the Proof of Concept is completed correctly in a timely fashion.
|
| 6. |
How are new Data Slicer shared test environments built?
Building a new Data Slicer shared test bed is a two step process. First, the customer must select an existing test bed for sharing or build a new test bed by running the necessary DDL statements or letting Move for DB2™ construct it. Second, once a test bed has been constructed, the Data Slicer Power Slicer Utility will alter it for test data sharing purposes. The only information required by the Power Slicer is a list of DB2 tables located in the shared test bed.
|
| 7. |
Does implementing Data Slicer require any changes to our DB2 application programs?
No, Data Slicer does not require any changes to application programs or nor does it impact application developer's jobs significantly.
|
| 8. |
Will we use Data Slicer to replace all of our replicated DB2 test beds (databases)?
No, probably not. Data Slicer is designed to primarily replace replicated Unit Test databases. Unit Testing is where most developers and testing personnel need to run many tests and to share test data the most. System Integration and Quality Acceptance (Assurance) test beds are not shared nearly as often and do not really require to be Sliced. Also, Performance and Stress Testing environments should not be Sliced either. As a new column is added to Sliced DB2 tables, DB2 program access paths may be different therefore invalidating your performance emulation results. Fortunately, these test beds do not usually need to be shared or, therefore, Sliced.
|
| 9. |
Will application developers notice any large changes to their current testing procedures?
No, application developers will not change the way they test their DB2 programs significantly, if at all. One of the absolute best advantages of Data Slicer is that developers simply point to a new shared database (test bed) and continue to run their same load jobs and test JCL.
The biggest changes noticed by developers and other testing personnel is that they will now be able to load, test and refresh test data all at the same time without affecting each other's results!
|
| 10. |
How do developers retrieve just their own Slice of shared test data?
Developers do not need to do anything if testing groups are already established, RACF or ACF2 security is set up, and DB2 Secondary Authid's are in place. As developers run their tests, their Secondary Authids will determine which Slice of data is passed back to their DB2 programs. If greater granularity is required for sharing test data, for example, each person needs their own, some additional set up steps can quickly provide this capability.
|
| 11. |
How do developers retrieve just their own Slice of shared test data?
Developers do not need to do anything if testing groups are already established, RACF or ACF2 security is set up, and DB2 Secondary Authid's are in place. As developers run their tests, their Secondary Authids will determine which Slice of data is passed back to their DB2 programs. If greater granularity is required for sharing test data (for example, each person needs their own), some additional set up steps can quickly provide this capability.
|
| 12. |
Does Data Slicer extract test data from production DB2 tables and/or legacy files?
No, Data Slicer does not contain any test data subsetting functionality. Data Slicer is a shared test environment only that is loaded using Princeton Move for DB2™, File-Aid/RDX™, or the IBM LOAD utility running in INSERT mode.
|
