implementing knowledge bases on secondary storage (abstract only)  in the past, many knowledge representation (kr) schemes in artificial intelligence (ai) research have assumed a primary storage-resident knowledge base. this approach to knowledge base implementation is becoming less feasible with current demands and expectations for ai-based software, in particular, large knowledge systems. the incorporation of secondary storage-resident knowledge bases into knowledge systems requires considerable rethinking with respect to knowledge structures and knowledge system design. it is the premise of this paper that there are many potential applications for knowledge systems that are based on a tightly-coupled system design, in which traditional ai kr schemes are modified to incorporate file processing techniques, e.g., hashing and signatures.  researchers in both ai and the database field are currently experimenting with a variety of approaches to "merging" ai and database technology. essentially, there are four approaches:  develop a simple interface between an ai development system, such as prolog, and a database system, such as ingres, i.e., a loose- coupling;  extend a database system to accommodate ai tasks, e.g., add inferencing capabilities;  extend an ai development system by adding database capabilities; and  develop a tightly-coupled system with its own ai and database capabilities.  although these four approaches to incorporating secondary storage residency into knowledge systems are very important ones, there is also much potential for incorporating specialized, file processing techniques, i.e., developing systems for applications that do not demand full database-level capabilities \---a simplified approach to (4) above. for example, there may be applications that demand large knowledge bases, and therefore require the efficient use of secondary storage, but that do not require concurrent access, recovery capabilities, and so on. in these cases, we believe that knowledge systems with specialized input/output processing, tailored to a particular kr scheme, will be completely adequate and self-contained, and possibly more efficient and cost-effective. knowledge bases implemented in primary storage on computers with large virtual storage capabilities cannot substitute for the above.  there are many issues to be addressed in designing a knowledge system with secondary storage processing, based on either file or database processing techniques. one important issue concerns the lack of (traditional) primary keys during inferencing and query resolution [1]. we are currently investigating partitioning schemes with hashed partitions, where each partition contains "homogeneous" facts and/or rules and uses traditional ai kr schemes, e.g., frame-like knowledge structures, such as prolog structures, and tuples in prolog relations.  another related issue is partition size, i.e., knowledge-partition resolution and granularity. partition size can be determined by several criteria, including available primary storage, "natural" partition size of "like" knowledge, traditional bucket size criteria for file processing, and inferencing techniques.  furthermore, the implementation language has a bearing on some of these issues. for example, with prolog there must be an explicit accommodation of the default backtracking technique, whereas with lisp the programmer is free to tailor the backtracking algorithm to the knowledge structures from the outset. as another example, consider the default indexing techniques used with prolog. some prolog implementations index on the first component of a relation only [2]. additional code must be introduced to supplement and properly override such defaults.  by tightly coupling traditional kr schemes with partitioning, indexing, and hashing schemes it will be possible to develop an efficient knowledge system capable of managing a large knowledge base.  jerry d. smith