I don't think you can improve that too much if you still want to use a datatable, because that is where your bottleneck is performancewise.
You are still doing the actual load of data as fast as in SSMS, however, when populating the datatable, you get a performancedrop in exchange for a quickly defined object structure to use later on.
You could of course improve it by skipping the datatable and instead load the resultset in custom objects. This is maybe not possible depending on the rest of your implementation. Another solution is to try to reduce the number of rows/columns you get back which is what I would opt for first and foremost.
Some links:
No comments:
Post a Comment