«

I'm building my first webservice and I've some doubt about the life's
cycle.
Teorically a webservice is consumed and dead just after it has released
the information for which it has been built.

So, because I've to use the webservice like a bridge to store sql info
on a SQL Server table, how can I make sql connection persistent?
Just to avoid sql connection create and destroy process every time.

Thanks
Andrea

Hi Andrea.
if you need a persistent connection, how about a replication scenario
instead of Web svc?
On the other side, Web svc consuming is tipically disconnected, while svc
itself could be or not.

"Andrea" <> ha scritto nel messaggio
news: oups.com...
> I'm building my first webservice and I've some doubt about the life's
> cycle.
> Teorically a webservice is consumed and dead just after it has released
> the information for which it has been built.
>
> So, because I've to use the webservice like a bridge to store sql info
> on a SQL Server table, how can I make sql connection persistent?
> Just to avoid sql connection create and destroy process every time.
>
> Thanks
> Andrea
>

..NET keeps a pool of SQL connections 'alive', this way SQL connections are
re-used and not recreated every time you do a 'cn.open'. for SQL connections
to be 'pooled' they'd have to have to exact same ConnectString.

HTH,
Jurjen.

"Andrea" <> wrote in message
news: oups.com...
> I'm building my first webservice and I've some doubt about the life's
> cycle.
> Teorically a webservice is consumed and dead just after it has released
> the information for which it has been built.
>
> So, because I've to use the webservice like a bridge to store sql info
> on a SQL Server table, how can I make sql connection persistent?
> Just to avoid sql connection create and destroy process every time.
>
> Thanks
> Andrea
>