모든 공개 기록

IT 위키에서 사용할 수 있는 모든 기록이 표시됩니다. 기록 종류나 사용자 이름(대소문자 구별) 또는 영향을 받는 문서(대소문자 구별)를 선택하여 범위를 좁혀서 살펴볼 수 있습니다.

• 2024년 12월 13일 (금) 01:40 Scapegoat 토론 기여님이 Multiversion Concurrency Control 문서를 만들었습니다 (Created page with "'''Multiversion Concurrency Control (MVCC)''' is a concurrency control method used in database systems that allows multiple versions of a data item to exist simultaneously. It ensures consistent reads without locking and provides high concurrency by maintaining transaction isolation. ==Key Concepts== *'''Data Versioning:''' MVCC creates a new version of a data item for every write operation, enabling transactions to access consistent snapshots. *'''Timestamps:''' Each tr...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:39 Scapegoat 토론 기여님이 Timestamp-Based Protocol 문서를 만들었습니다 (Created page with "'''Timestamp-Based Protocol''' is a concurrency control mechanism in database systems that uses timestamps to order transactions, ensuring serializability. Each transaction is assigned a unique timestamp when it begins, and the protocol uses these timestamps to determine the execution order of conflicting operations. ==Key Concepts== *'''Timestamp:''' A unique identifier (usually based on the system clock or a counter) assigned to each transaction when it starts. *'''Rea...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:35 Scapegoat 토론 기여님이 Lock-Based Protocol 문서를 만들었습니다 (Created page with "'''Lock-Based Protocol''' is a concurrency control mechanism in database systems that ensures transaction isolation by managing access to data items through locks. Locks prevent simultaneous transactions from interfering with each other, ensuring data consistency and serializability. ==Key Concepts== *'''Lock:''' A mechanism that restricts access to a data item for concurrent transactions. *'''Lock Modes:''' **'''Shared Lock (S):''' Allows multiple transactions to read a...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:33 Scapegoat 토론 기여님이 Two-Phase Locking 문서를 만들었습니다 (Created page with "'''Two-Phase Locking (2PL)''' is a concurrency control protocol used in database systems to ensure serializability of transactions. It operates in two distinct phases where locks are acquired and released in a specific order, preventing conflicts between concurrent transactions. ==Key Concepts== *'''Locking Protocol:''' Transactions acquire locks on data items before accessing them and release locks when no longer needed. *'''Serializability:''' 2PL guarantees that the r...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:31 Scapegoat 토론 기여님이 Concurrency Control 문서를 만들었습니다 (Created page with "'''Concurrency Control''' is a mechanism in database management systems (DBMS) that ensures correct and consistent transaction execution in a multi-user environment. It prevents issues such as data inconsistencies and anomalies by managing simultaneous access to the database. ==Key Concepts== *'''Transaction:''' A sequence of database operations that are executed as a single logical unit of work. *'''Isolation:''' Ensures that each transaction is executed independently w...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:28 Scapegoat 토론 기여님이 Isolation Level (Database) 문서를 만들었습니다 (Created page with "'''Isolation Level''' is a property in database transaction management that defines the extent to which transactions are isolated from each other. It determines how and when changes made by one transaction are visible to other concurrent transactions, affecting the trade-off between consistency and concurrency. ==Key Concepts== *'''Transaction Isolation:''' Ensures that concurrent transactions do not interfere with each other inappropriately. *'''Anomalies:''' Lower isol...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:26 Scapegoat 토론 기여님이 Non-Repeatable Read 문서를 만들었습니다 (Created page with "'''Non-Repeatable Read''' is a concurrency problem in database systems that occurs when a transaction reads the same data twice and gets different results due to modifications made by another transaction in the meantime. This inconsistency arises when isolation levels do not guarantee stability for repeated reads of the same data. ==Key Concepts== *'''Unstable Reads:''' The data read by a transaction changes during its execution because another transaction modifies it. *...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:26 Scapegoat 토론 기여님이 Dirty Read (Database) 문서를 만들었습니다 (Created page with "'''Dirty Read''' is a concurrency problem in database systems that occurs when a transaction reads uncommitted changes made by another transaction. This can lead to inconsistent or incorrect data being used in the reading transaction, especially if the changes are later rolled back. ==Key Concepts== *'''Uncommitted Data:''' Data modified by a transaction that has not yet been committed to the database. *'''Concurrency Issue:''' Dirty reads are a type of Database Anomal...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:23 Scapegoat 토론 기여님이 Precedence Graph 문서를 만들었습니다 (Created page with "'''Precedence Graph''', also known as a '''Serializability Graph''', is a directed graph used in database systems to determine the serializability of a transaction schedule. The graph represents the order of operations across transactions and helps identify potential conflicts that could prevent a schedule from being equivalent to a serial schedule. ==Key Concepts== *'''Nodes:''' Represent individual transactions in the schedule. *'''Edges:''' Indicate a precedence (or d...") 태그: 시각 편집
• 2024년 12월 13일 (금) 01:20 Scapegoat 토론 기여 계정이 생성되었습니다