Solved

Redo Logs for SQL Server

Posted on 2004-10-05
3
3,966 Views
Last Modified: 2008-03-06
Oracle has Redo Logs for 'Undeleting' records.

What is equivalent in SQL Server?

I need to find any reference to records that were deleted.

Thanks!

RipHerANewOne!
0
Comment
Question by:RipTide
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 34

Assisted Solution

by:arbert
arbert earned 50 total points
ID: 12232782
There really isn't  a "direct" counterpart.  SQL Server has the transaction log that (if the recovery mode is setup right) will allow you to do point in time restores to the database.  However, you can't browse the transaction log without a third party tool (logexplorer from lumigent is nice http://www.logexplorer.com)
0
 
LVL 42

Accepted Solution

by:
Eugene Z earned 75 total points
ID: 12232809
Answer: transaction log  
[from http://www.akadia.com/services/sqlsrv2ora.html]

Each SQL Server transaction log has the combined functionality of an Oracle rollback segment and an Oracle online redo log. Each database has its own transaction log that records all changes to the database and is shared by all users of that database. When a transaction begins and a data modification occurs, a BEGIN TRANSACTION event (as well as the modification event) is recorded in the log. This event is used during automatic recovery to determine the starting point of a transaction. As each data modification statement is received, the changes are written to the transaction log prior to being written to the database itself. For more information, see "Transactions, Locking, and Concurrency" later in this paper.

SQL Server has an automatic checkpoint mechanism that ensures completed transactions are regularly written from the SQL Server disk cache to the transaction log file. A checkpoint writes any cached page that has been modified since the last checkpoint to the database. Checkpointing these cached pages, known as dirty pages, onto the database, ensures that all completed transactions are written out to disk. This process shortens the time that it takes to recover from a system failure, such as a power outage. This setting can be changed by modifying the recovery interval setting by using SQL Server Enterprise Manager or with Transact‑SQL (sp_configure system stored procedure).
0
 
LVL 34

Assisted Solution

by:arbert
arbert earned 50 total points
ID: 12232884
transaction log is not the same thing as a redo log....but it's as close as you get...if the recovery model is set to simple, you won't be able to obtain the same information you would from a redo log....
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to shrink a transaction log file down to a reasonable size.

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question