Thank you for your information. Rebooting the server or restarting SQL
Server would be a "last chance" option. The reason why I ask this question
here is that because the TCP connection remains opened even after I close
SQL Server Management Studio. So it seems that it's a Windows Server
problem, not an SQL Server one.
Pierrot
"Anthony [MVP]" <(E-Mail Removed)> wrote in message
news:%23gd65%(E-Mail Removed)...
> shutdown -r
> or net stop mssqlserver,
> You might do best to ask this in a SQL Server newsgroup, where you could
> find the ways of closing open connections, e.g
> http://support.microsoft.com/kb/171224/en-us
> Anthony,
> http://www.airdesk.com
>
>
> "wpher56" <(E-Mail Removed)> wrote in message
> news:uHAXL7#(E-Mail Removed)...
>> Hi
>> My SQL Server 2005 connects to an Oracle Server, but there is a problem:
>> the
>> TCP connections are left opened (ESTABLISHED). By the end of the day, I
>> have
>> more than a thousand opened TCP connections! Until we find the cause of
>> this
>> behaviour, I would like to create a small batch file that would run at
>> 4am
>> and that closes the TCP connections of the previous day. Could someone
>> help
>> me doing this ?
>> Many thanks in advance
>> Pierrot
>>