|
|
|
|
Browse by Tags
All Tags » Trace (RSS)
-
(Note: I have re-written parts of this post in the light of the comments that SP1 of 2012 include Complete tools.)
I have decided to revisit the topic of whats included in Express Edition, with focus on the tools. I have a couple of reasons for this:
In my 2011 post, I never tried to connect from Express SSMS to a non-Express ...
-
Last week at SQL Bits #8 in Brighton, England, SQL Sentry (my employer) announced its partnership with DBSophic, makers of the Qure workload management suite. Qure Workload Optimizer is a tool aimed at analyzing a workload and providing suggestions to improve the overall performance of that workload. These suggestions can range from adding and ...
-
Here are the Connect items I'd like to draw your attention to this week. I have abandoned the idea of trying to keep track of vote counts and overall rating. Being lazy might be a small part of it, but it is mostly because I just don't think it makes sense to assume that my postings are all that influence Connect behavior. I know ...
-
This is a recommendation I believe is worth repeating from time to time: Make sure you match data types when you write TSQL code. Else you in most cases end up with an implicit data type conversion. And in worst case, this conversion is performed at the column side - not the literal side of your query. What does that mean? Consider below:
WHERE ...
-
I just read the question how to find out when autogrow in tempdb happened. And again I want to push for the default trace. The simple answer is that you already have this information available, just go and get it! (Unless you explicitly disabled the default trace, of course...)
Adjust the file name for your most recent default trace file in below ...
-
Paul Randal writes:
''Kimberly mentioned that SQL Server has a 'black-box' trace, similar to an aircraft flight-recorder, which I'd never heard of. It's an internal trace that has the last 5MB of various trace events and it's dumped to a file when SQL Server crashes. This can be really useful if you're troubleshooting an issue that causing SQL ...
|
|
|
|
|