Profile_bird

Hey there! KimberlyLTripp is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving KimberlyLTripp's tweets.

Already using Twitter
from your phone? Click here.

KimberlyLTripp

  1. @SQLSarg IOs are in 1, 8 or 32 page requests (generally - but can be more) recommended block size (for RAID format) is 64K.
  2. [BLOG] Data Dude moving into lower priced VS Editions in VS 2010 - excellent! http://bit.ly/3jeLuh Yippie!! #sql #vs2010
  3. @paulrandal You'll be looking awhile given your attitude! LOL. And, I'm about to start back up at 1:30 so don't tweet behind my back! :)
  4. Discussion/Q: Where do I spend most of the design time (in DBs)? A: on the monsters (the 10 or so largest [most annoying] tables)!
  5. {BLOG] I've updated my MVP Deep Dives post to have corrected names (in pic) *and* links to author chapters: http://bit.ly/42YNDj. Just FYI.
  6. {BLOG] Travel tips re: @kekline tagged me here: http://bit.ly/EF6FT so my response is here: http://bit.ly/1dkGOJ. Enjoy!
  7. [BLOG] Interviews with MidnightDBA are live: http://bit.ly/3xmzgh. (and, yes, I know that most of you already know :). Enjoy!
  8. @dsfnet re:INCLUDE. Yes, this is to help indexes cover more queries without sorting and/or widening the upper levels of the tree.
  9. @dsfnet re: truncate partition isn't necessary. Just as fast to switch out and drop. But, I think you want only one step, right? Not speed?
  10. @MidnightDBA Why do you suspect perf degraded by nested views? It shouldn't be - but can happen during opt. not nec. view's fault.
  11. Updated blog post with pic from PASS & links to most authors & editors blogs: http://bit.ly/42YNDj. Enjoy!
  12. #sqlconn @SQLvariant VLFs should be 16 per 8GB. Exact *max* depends. If file is small 100s is very bad. If the file is large, it depends.
  13. #sqlconn Some people said they liked my troubleshooting (and especially the explanation) on showing what was wrong. So, in the end was OK.
  14. @buckwoody Yeah, I have that two... helps if I had run it.
  15. #sqlconn #sqlpass Just blogged about the SQL Server MVP Deep Dives title (with a pic from launch at PASS): http://bit.ly/42YNDj. Enjoy!
  16. #sqlconn See Part 9 of my msdn webcast. The entire thing is about creating server-side traces: http://bit.ly/2RWVBZ. Enjoy!
  17. #sqlconn note to self - always RE-restore base "demo database" so that the last demo's indexes don't mess you up! (which I usually do...) :(
  18. @SQLVariant Technically the first log file should never be removed/deleted. Ideally, it's appropriately sized and on fast drive/LUN.
  19. @SQLVariant A better way get rid of large log would be to change to SIMPLE rec model. Run a checkpt. Use SHRINKFILE & alter to correct size.
  20. @StaciaMisner #sqlconn LOL. I think he means more that people should chart it in some way. Not specific to pie charts. U need blog 4Y tho.