Viewing 15 posts - 901 through 915 (of 1,192 total)
For that it is much better to use the appropriate comparisons with >= and < on the beginning and end dates of the range.
Even though you can use wildcards...
July 28, 2015 at 1:13 pm
The only way I know is the one I mentioned before, creating a snapshot and reverting to it.
That will rebuild the log file as a 500 KB file. It's probably...
July 27, 2015 at 9:50 pm
July 27, 2015 at 4:32 pm
Also, if it is related to model, the model configuration would have to be even more unusual, since for the initial VLFs to be that size, the database would have...
July 27, 2015 at 3:35 pm
Check the columns...the data is misaligned with the actual values because the header RecoveryUnitID takes up as much space as the first two columns of data.
You just have to manually...
July 27, 2015 at 3:02 pm
The minimum number of VLFs is 2, which you're already at. That's why you can't shrink the log anymore.
You're essentially at the minimum size of the log given how...
July 27, 2015 at 2:32 pm
With respect to the tempdb log, checkpoints are different for tempdb, and only automatically run when the log hits 70% used (see here: http://www.sqlskills.com/blogs/paul/what-does-checkpoint-do-for-tempdb/).
So, if your tempdb sits around idle...
July 27, 2015 at 12:30 pm
Heh, no worries. These things happen 🙂
As it turns out, I think I may have the misfortune of being the bearer of more bad news. It seems that solution relies...
July 21, 2015 at 3:51 pm
Thanks for the update! That is rather strange indeed.
I'm glad you figured it out!
July 21, 2015 at 3:03 pm
Luis posted his while I was typing, but here's my solution as well:
CREATE TABLE #foo
(
ItemID int,
StartDate datetime,
...
July 21, 2015 at 1:56 pm
Well, the plot thickens. At least in 2008 R2, the page locks held at the end of the second INSERT are for the new pages allocated by the second INSERT....
July 20, 2015 at 10:04 am
Confirmed. My 2014 instance behaves the same as yours. I end up with 25 locks held after the second INSERT.
Following what you posted regarding the Lock Acquired events, I also...
July 18, 2015 at 1:21 pm
That's perfectly understandable! Testing fairly esoteric SQL Server behavior is not high on the list of Saturday evening-appropriate activities 🙂
I'll tackle it from the other end and run the...
July 18, 2015 at 12:34 pm
Understood. I just wasn't sure how much of the post was from after your edit, so I just wanted to double-check whether that lock info in it was for 2014...
July 18, 2015 at 12:07 pm
Interesting...I hadn't even bothered to try 2014 yet. There were so many variables to control for just with 2008 R2 and 2012 🙂
I guess at some point I'll extend my...
July 18, 2015 at 11:03 am
Viewing 15 posts - 901 through 915 (of 1,192 total)