network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 2 years |
| seen | Dec 5 '12 at 17:46 | |
| stats | profile views | 2 |
|
Nov 8 |
comment |
Silently corrupted table after power-related shutdowns, records missing, *scrambled*? @Jon Yeah, I read about that, I'll do a full re-index over the weekend so it actually calculates all the checksums. I'm recovered from the backups, so we'll see what happens. This is a fairly new server, I really hope we're not losing a drive already... |
|
Nov 8 |
comment |
Silently corrupted table after power-related shutdowns, records missing, *scrambled*? Good call, it was on torn page detection, I bumped it up to checksum. Can a hdd-level issue cause such a broad and "well-behaved" problem, without checksums on? |
|
Nov 8 |
asked | Silently corrupted table after power-related shutdowns, records missing, *scrambled*? |
|
Sep 12 |
awarded | Supporter |
|
Jun 15 |
comment |
How can I tell if my SQL Server DB performance is hardware-limited? Nope, exactly the same. Ditto for DBCC updateusage. |
|
Jun 13 |
comment |
How can I tell if my SQL Server DB performance is hardware-limited? I grabbed a couple of queries to order and filter the relevant info from waitstats, and it didn't tell me much (see my comment on the original item). |
|
Jun 13 |
comment |
How can I tell if my SQL Server DB performance is hardware-limited? Upgrading to 2008 seems to be a quick fix, because even 2008 Express with its 1 CPU 1 GB RAM limits has completely solved the problem. Still, I'd like to understand why/how... |
|
Jun 13 |
comment |
How can I tell if my SQL Server DB performance is hardware-limited? Tried this in the 2008 Express instance I set up - dm_exec_query_stats doesn't seem to be present? |
|
Jun 13 |
comment |
How can I tell if my SQL Server DB performance is hardware-limited? Well, it's not entirely hardware at least - I put an instance of 2008 Express side-by-side on the test machine. 2000 times are still in the same range, 2008 times are all < 20ms. The waitstats don't seem to clarify the difference. After clearing stats and on an identical app test, 2000 had PAGEIOLATCH_SH wait time of 2.48s, avg wait 4ms. 2008 had 2.14s, avg wait 2ms. Which is better, but doesn't explain the 10-fold improvement in actual response times - is that just in generic engine enhancements from 2000 to 2008 that aren't reflected in stats? |
|
Jun 13 |
awarded | Scholar |
|
Jun 13 |
awarded | Student |
|
Jun 10 |
asked | How can I tell if my SQL Server DB performance is hardware-limited? |
