Viewing 15 posts - 3,901 through 3,915 (of 5,843 total)
common culprits for large tlog files:
1) FULL recovery mode but not doing ANY tlog backups
2) leaving long running tranactions open even in SIMPLE mode. then committed transactions cannot be...
August 19, 2010 at 8:47 am
Steve Jones - Editor (8/17/2010)
August 19, 2010 at 8:44 am
did you resolve your problem? parallelism could be result of missing index, which could improve performance a thousand times or more. You might also be getting too many...
August 18, 2010 at 7:19 am
1) trigger
2) blocking
3) unindex foreign keys
4) horrible tlog write performance
5) server being crushed by other activity
August 18, 2010 at 7:17 am
1) search web for track_waitstats_2005 to get a very good script to do wait stats analysis by time-spread analysis.
2) I disagree with previous poster that CXPACKET waits dont' indicate a...
August 18, 2010 at 7:16 am
I would like to put in a plug here for the amazing FREE tool SQLJobVis. Gives you a Gantt chart of job schedules/executions. VERY handy for detecting overlaps...
August 18, 2010 at 7:06 am
Nice stuff Tim - oh, and good to see you at SQL Saturday 28 in Baton Rouge this w/e!!
Another thing I have found to be important and telling...
August 16, 2010 at 2:59 pm
You should also analyze wait stats and especially IO stalls to find out where the process is bottlenecking. tempdb IO performance issue here anyone? 😀
August 12, 2010 at 8:50 am
Here is the "bible" for deadlock troubleshooting: http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx
Note there are 2 additional parts to this blog series.
August 12, 2010 at 8:47 am
FreeHansje (8/11/2010)
Arrgghh!Initial size is that big, I never looked for it!! Somebody kick me!
Tnx.
Maybe it is that big because someone else KNEW it needed to be that big?? No...
August 12, 2010 at 8:45 am
The "spamming" you describe is from LINKED SERVER activity. Bad stuff there. I have had several clients get several orders of magnitude improvement from replicating out stuff that...
August 12, 2010 at 8:42 am
Microsoft is WAY behind the curve on this topic, and PDW will take at least another 18 months or so to be anywhere close to where it should be. ...
August 11, 2010 at 7:02 am
Paul White NZ (8/10/2010)
The query optimiser will only consider looking for parallel plan alternatives if the best serial...
August 11, 2010 at 6:54 am
ejbatu1 (8/9/2010)
August 10, 2010 at 7:03 am
Perry Whittle (8/9/2010)
let me re phrase that.New in SQL Server 2005!
I still refer to numerous 2005 features as "new". When you have been using the product since 6.5 first...
August 10, 2010 at 7:00 am
Viewing 15 posts - 3,901 through 3,915 (of 5,843 total)