Keyed vs. Nonkeyed Physical Files
From: Cynthy Johnson To: All
I need some help and supporting facts. As I started designing an application, I began to wonder whether the physical files should be keyed or whether they should be nonkeyed and use logical file access paths? I've found some pretty strong opinions on this topic. I was told that I should always key my physical file. I don't believe the issue is that simple. I think that there are pros and cons of always keying physical files. I need to present some strong arguments on both sides of the issue to my company. Can anyone help me out?
From: James Coolbaugh To: Cynthy Johnson
I have always used keyed physical files and have never run into any problems with them. When you key a physical file, all you are doing is attaching an index to the physical file. The data remains in input order until you reorganize or copy the data. Having a keyed physical allows you to have a consistent method of getting to the data. Of course, I use keyed physical files only when I have a unique key to the data in the file. If the key is not unique or there isn't really a standard method to retrieve an individual record, I don't really worry about it. I don't have any strong feelings on this one, except that I see no reason to limit the placement of keys on a physical file. If your database design is good, then it won't matter where your indexes are.
From: Pete Halsted To: Cynthy Johnson
The software that we use does not have any keyed physical files. They are all logical files. So far the things I like are:
1. In a major conversion you can delete all logical files, perform the conversion and recreate logical files much more quickly.
2. You do not run into the problem of not being able to change a key field since there are truly no keys.
On the down side, it does add another step in maintenance. You have more files to maintain since every file has at least one logical file.
From: Ted Holt To: Cynthy Johnson
I use both methods. I wrote an article, "Designing Databases for Flexibility" (MC, September 1990), which briefly touched on this. The advantage to not keying the physical file is that you don't have to delete all the logicals if the primary key changes. Or to state it backwards, if you have to change the key over a physical file, you have to delete and recreate all the logicals.
Other than that, I don't really think it makes that much difference.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online