Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Need some information 1
- Thread starter Ravi29
- Start date
-
1
- #3
Here's what happens:
You have a database with 10 rows. You update one row, that's a transaction and you now have one row in the transaction log. You insert 10 more rows, again that's a transaction and you now have 11 rows in the log. You update five of those rows, yep, another transaction and you now have 16 rows in the log. You delete five rows, and now there are 21 rows in the log, but only 15 rows in the database. As you see, the log is getting bigger that the database. If you never do a full backup of the database, or never truncate the transaction log, it is possible for the log to get several times larger than the database.
Please take a look at:
FAQ183-1534
FAQ183-345
and the Books Online for more information.
-SQLBill
You have a database with 10 rows. You update one row, that's a transaction and you now have one row in the transaction log. You insert 10 more rows, again that's a transaction and you now have 11 rows in the log. You update five of those rows, yep, another transaction and you now have 16 rows in the log. You delete five rows, and now there are 21 rows in the log, but only 15 rows in the database. As you see, the log is getting bigger that the database. If you never do a full backup of the database, or never truncate the transaction log, it is possible for the log to get several times larger than the database.
Please take a look at:
FAQ183-1534
FAQ183-345
and the Books Online for more information.
-SQLBill
Be aware that if you truncate the log manually, you cannot recover any data past the last backup. If your database is transaction-oriented, you should be doing transaction log backups periodically to keep the log size down and to give yourself the ability to recover as many transactions as possible. How often you do the transaction backups depends on your management and how much data they are willing to lose. (Get this in writing especially if they say anything more than an hour's worth!) We generally do these backups every 15-30 minutes depending on the traffic on the database. You can also perform large imports of data as nonlogged operations, but you should then follow them immediately with a full backup.
Truncation won't shrink the file size either, it just removes the records that have already been committed. You can periodically shrink the files, but they won't get any smaller unless you have recently run backup or manually truncated the log.
Truncation won't shrink the file size either, it just removes the records that have already been committed. You can periodically shrink the files, but they won't get any smaller unless you have recently run backup or manually truncated the log.
- Thread starter
- #5
hi!
Here every one said how i want to maintaine that log -file. Thanks for your kind of information.But shall you give me some more how i utilize that?. Suppose i have been created one database, within that i had created one table. This table involved more than one transaction such as insert some records,deleted some records and updated some records. Now i want to visulize what are the transaction made on that table. Is it possible from extracting infromation from log file?. If yes, tell me how i want to do.
Here every one said how i want to maintaine that log -file. Thanks for your kind of information.But shall you give me some more how i utilize that?. Suppose i have been created one database, within that i had created one table. This table involved more than one transaction such as insert some records,deleted some records and updated some records. Now i want to visulize what are the transaction made on that table. Is it possible from extracting infromation from log file?. If yes, tell me how i want to do.
- Thread starter
- #6
hi!
Here every one said how i want to maintaine that log -file. Thanks for your kind of information.But shall you give me some more how i utilize that?. Suppose i have been created one database, within that i had created one table. This table involved more than one transaction such as insert some records,deleted some records and updated some records. Now i want to visulize what are the transaction made on that table. Is it possible from extracting infromation from log file?. If yes, tell me how i want to do
Here every one said how i want to maintaine that log -file. Thanks for your kind of information.But shall you give me some more how i utilize that?. Suppose i have been created one database, within that i had created one table. This table involved more than one transaction such as insert some records,deleted some records and updated some records. Now i want to visulize what are the transaction made on that table. Is it possible from extracting infromation from log file?. If yes, tell me how i want to do
You can't do it with MS SQL Server. However, there is a third-party program that lets you look at the transaction log(s). I don't know the name off the top of my head. I'll look for it and let you know (unless someone else answers you first.)
-SQLBill
-SQLBill
Got the answer. It's Log Explorer by Lumigent (
However, check out these threads first:
thread183-85990
thread183-130322
thread183-111526
They have more on the subject of reading/viewing log files.
-SQLBill
However, check out these threads first:
thread183-85990
thread183-130322
thread183-111526
They have more on the subject of reading/viewing log files.
-SQLBill
- Thread starter
- #9
- Status
Similar threads
- Locked
- Question
- Locked
- Question
