I am using WCF with Sql Server. i wrote a TSQL to create a CURSOR, populated with a SELECT. this is executed from the client, leaving the connection open. The client then executes a FETCH to retrieve records, but the connection is closed. Any ideas how to keep the connection open would be apprecaited.
First off, you really, really, really don't want to do this. Leaving a connection open from the client will end up causing you to run out of connections since there are a limited number.
yeah, had considered that architecture. there are a couple of problems there. first, it creates a new query with each server hit. second, if data changes inbetween queries, the results change. a cursor would be perfect, this is exactly what it is for. if somehow the connection could be maintained on the server, and the client reconnect to it, or something.
the problem with the WCF forum is many features available in other platforms are not available in SIlverlight, so for Silverlight applications I prefer to stay here. but i do appreciate the suggestions.