Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 708

Transaction log is a list/history of modification executed by a database management system to guarantee ACID properties over crashes or hardware failures.

6
votes
why are those operations on the log file if they haven't been committed in the first place All operations, committed or uncommitted, are written in the log. A commit ensures that all log entrie …
answered Feb 16 '12 by Remus Rusanu
0
votes
You must check log_reuse_wait during the import process. Most likely you have a some long running transaction started at the beginning of the import that is pinning the log for the entire import durat …
answered Feb 12 '13 by Remus Rusanu
6
votes
You can import the data by using operations that can be minimally logged. See Operations That Can Be Minimally Logged and Prerequisites for Minimal Logging in Bulk Import. And you should consider red …
answered May 6 '13 by Remus Rusanu
1
vote
No. After you restored the database in your development environment it had become a different database. Re-attaching it back to production will replace the production database and all transaction that …
answered Feb 19 '13 by Remus Rusanu
5
votes
Start by investigating what is holding up the log reuse. Read Factors That Can Delay Log Truncation, look at log_reuse_wait_desc value is sys.databases. Based on what you find there, there could be se …
answered Oct 10 '12 by Remus Rusanu
11
votes
On a technical level: is this a good practice or not? I would say not. If the database is experiencing no activity at all during the business off hours, then taking the backups is very low overhe …
answered Jan 18 '16 by Remus Rusanu
7
votes
Most likely you did. Most cases database files, including transaction log, are configured for auto-growth. Auth-growth enables the file to increase its size as needed, any time is needed. The trigger …
answered Jan 31 '13 by Remus Rusanu
5
votes
the very first thing you have to do is to change AUTOSHRINK to false. There is absolutely no reason to ever have it true. See AUTOSHRINK: Turn it OFF!. Both operations you are attempting require a si …
answered Jan 3 '12 by Remus Rusanu
21
votes
In AGs writes can only occur on the primary. Shrink operations are writes. Therefore you must do the shrink on the primary. Note that the shrink may not shrink as much as you expect, your test on the …
answered Aug 13 '14 by Remus Rusanu
11
votes
You can view the individual rows that were deleted by looking for LOP_DELETE_ROWS operations still in the log: select * from fn_dblog(NULL, NULL) where Operation = 'LOP_DELETE_ROWS' If the log was …
answered May 28 '12 by Remus Rusanu
4
votes
No. The recover process always starts from a full database backup and then it applies the log backups. If your database has no backups then it is not in full recovery mode. Untill you actually take a …
answered Oct 22 '09 by Remus Rusanu
8
votes
How to reduce the size of transaction log file without shrink process (Because it’s Bad – Increases Fragmentation – Reduces Performance) That is not true. log shrink is quite benign, you are thin …
answered Mar 7 '14 by Remus Rusanu
6
votes
The log vs. data separation is sound advice, but the devil is always in the details. A write intensive workload that commits frequently requires the log stream to flush to disk as fast as possible. Th …
answered Apr 22 '14 by Remus Rusanu
6
votes
REORGANIZE (as in ALTER INDEX ... REORGANIZE) is a very fast operation (well, mostly...), which require small amount of log, can be interrupted at any moment and resumed later, and works internally in …
answered Jan 4 '12 by Remus Rusanu
14
votes
At the very least you need to consider differential backups. Unless copy-only on the full is used, your next diff backup will be off. Copy-Only Backups: Copy-only full backups (all recovery models …
answered Jul 8 '13 by Remus Rusanu

15 30 50 per page