Connection pool problems with services

[Rilez]

Hi all

I've got a series of windows services that connect to my database to perform operations to data loads to progress them from one state to another. This all works fine apart from the sql server service has to be stopped and started every night to enable backups. When sql comes back up the services will not work until they are stopped and started themselves. There are ways we can get round this but is there anything I can do in the programming to stop this happening? Can I force it not to use connection pooling - these are backend - single process threads so I don't care about pooling in the slightest

Thanks

 

[chrissie1]

This all works fine apart from the sql server service has to be stopped and started every night to enable backups.

SINCE WHEN??????

Mine never has to.

Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]

 

[Rilez]

power quest will not take images of drives while they are in use. It forces the service to stop and then start again

 

[chrissie1]

And this while backup exec and sql-server can do the job without stopping the service. Mmmmm perhaps time for a change in strategy?

Christiaan Baes
Belgium

I just like this --> [Wiggle] [Wiggle]

 

[Rilez]

We use powerquest as we want to take an image of the entire server to enable disaster recovery.

I can't change the companies strategy just because of this problem, however tempting that might be

Thanks