메뉴 건너뛰기
.. 내서재 .. 알림
소속 기관/학교 인증
인증하면 논문, 학술자료 등을  무료로 열람할 수 있어요.
한국대학교, 누리자동차, 시립도서관 등 나의 기관을 확인해보세요
(국내 대학 90% 이상 구독 중)
로그인 회원가입 고객센터 ENG
주제분류

추천
검색
질문

논문 기본 정보

자료유형
학술저널
저자정보
저널정보
한국정보기술학회 한국정보기술학회논문지 韓國情報技術學會論文誌 제3권 제5호
발행연도
2005.11
수록면
73 - 88 (16page)

이용수

표지
📌
연구주제
📖
연구배경
🔬
연구방법
🏆
연구결과
AI에게 요청하기
추천
검색
질문

초록· 키워드

오류제보하기
In a Main Memory Database (MMDB) system, the primary copy of the database resides in volatile main memory as opposed to Disk Resident Database (DRDB) systems where the database is on disk. The perception of where the data resides is important. With an MMDB the DBMS software is designed assuming that the data is memory resident. With a DRDB the DMBS software is designed assuming the data is stored on disk and I/O is required to access the data [1]. MMDB systems need not perform I/O operations for database applications. Thus, they are ideal for applications that require high throughput and a fast response time. With the increasing demand for high-performance systems and the steady decrease in memory cost, MMDBs have become an attractive alternative to DRDBs [2]. This is especially the case for telephone switching applications, mobile computing applications and real-time systems, i.e, applications that require high throughput and fast response time [3]. Commercial 54-bit systems can support main memories of tens of gigabytes. It can be expected that the use of MMDB in an application requiring fast response time will be growing since larger volume of memory resident data allows faster processing of transactions Due to the volatility of main memory, MMDB complicates database recovery issues. Database recovery techniques ensures that any erroneous database state due to transaction, system, or media failure can be repaired and restored into a consistent state from which normal processing can resume. A main memory recovery algorithm, must do much more than the disk based recovery algorithm to guarantee atomicity, durability of transactions and database integrity without sacrificing the performance advantages of MMDB. This problem has been recognized and several techniques for MMDB recovery have been proposed. On this paper we described MMDB model, briefly mentioned various different .recovery techniques, and discussed log-based method and its components in detail. We focused on logging, checkpointing, and reloading.

목차

Abstract
Ⅰ. Introduction
Ⅱ. MMDB Recovery Techniques
Ⅲ. Case Studies
Ⅳ. Summary and Conclusion
Reference

참고문헌 (0)

참고문헌 신청

함께 읽어보면 좋을 논문

논문 유사도에 따라 DBpia 가 추천하는 논문입니다. 함께 보면 좋을 연관 논문을 확인해보세요!

이 논문의 저자 정보

최근 본 자료

전체보기

댓글(0)

0

UCI(KEPA) : I410-ECN-0101-2009-566-016511708