A "long" execution time for your query can have multiple causes. How big is each record? What speed is the network? I'm starting with these, as it seems to be the load-time that's your biggest bottleneck.
Can you show us how you load your data?
Have you tried comparing it to other compatible providers? (is ODBC available there?)
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
If you are finding that actually establishing the connection, in the first instance, is slow, this is quite common with most databases. The way to get round this is to use a connection pool where inactive connections are stored ready for use again.
I was wondering, if there is any way to create out of office rules (Reply-With Templates, forwardings... http://office.microsoft.com/en-us/outlook-help/send-out-of-office-notices-automatically-with-an-exchange-account-HP001232830.aspx#BM2[^]) in Exchange 2010 using c#? (Preferably EWS)
I know that this can be done in Exchange 2003 using MAPI, but I was unable to find any Information for Exchange2010...
I would advise you to examine very carefuly your use of the streams and the WebResponse -- also avoid trying to reuse them -- this is an inherently asynchronous process and trying to create an SMS bulk texting application is not what those classes are intended to do -- it is one thing to use them to mimic browser fetches, but quite another to use them statically for multiple texts.
At the very least, close them and get them each time -- the Response -- are you reading to the end and closing the response?