FULL RECOVERY
|
BULK LOGGED
|
SIMPLE RECOVERY
|
WAL concept 100%
applicable. Every transaction write into transaction log
|
WAL Concept is
applicable only except bulk transactions.
|
WAL concept 100%
applicable.
Every transaction
write into transaction
Log
|
Transactions are fully
logged
|
Transactions are
minimally logged
|
Transactions are fully
logged
|
Point in time recovery
is possible
|
Point in time recovery
is not possible
|
Point in time recovery
is not possible
|
No data loss or very
minimal data loss
|
Data loss only when we
perform bulk operation
|
Data loss chances are
very high
|
Performance impact is
slight
|
Performance impact is
slight in normal transaction but where as in bulk transaction no major performance
impact
|
No performance impact
|
Disk consumption is
high
|
Disk consumption is
high when normal transactions but in bulk Disk consumption is low
|
Disk consumption is
Less
|
Use for production
OLTP environments
|
Use for production
when there is any bulk transactions
|
Always use for
development servers
|
Labels
- Differences (38)
- MongoDB (13)
- MySQL (10)
- Oracle (6)
- ORACLE DBA (1)
- Performance Tuning (13)
- PTuning (3)
- Scenarios (4)
- Scripts (35)
- SQLDBA (99)
- SQLDeveloper (66)
- SSIS (5)
- SSRS (8)
- Troubleshooting (37)
Monday, 2 May 2016
Full Vs Bulk Logged Vs Simple Recovery models
Labels:
SQLDBA
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment