9

I made a few changes to the Data Explorer to address this issue, and ported some of the queries along the way to use Dapper. As part of those changes I reworked the code to pass the QueryResults object around a bit more instead of converting to and from a JSON string all of the time to save the request a bit of work, and hopefully didn't break anything in the process.

I also updated the schema used to validate the execution plan XML before transformation, because SQL Server started adding the undeclared ForceScan attribute to the output that's currently causing that feature to fail with " The 'ForceScan' attribute is not declared."

Changes can be found here: http://code.google.com/r/tmslft-sede/source/list

Improve this question
2
  • Awesome, thanks! will looks at this first thing next week unless rchern beats me to it
    – waffles
    Commented Sep 30, 2011 at 10:43
  • Cool! I've got a number of things on my Data Explorer to-do list, so hopefully I can find some more time to start poking around too.
    – Tim Stone
    Commented Sep 30, 2011 at 10:57

1 Answer 1

Reset to default
2

Done, merged it in ... keep the patches coming !!!

Improve this answer
1
  • Nifty! Next one's almost ready, client-side updates this time :)
    – Tim Stone
    Commented Oct 5, 2011 at 0:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .