Connections Timed-Out

Hello, All!
Good Afternoon!
I'm having a strange situation in my SQL SErver 2000 SP3a with 4 Processors,
4GB of RAM and high-end disk sub-system.
I migrate a specific database from another instance with SQL SErver 2000 SP3a
too to this new server with more hardware resource than another one.
The application that access this DataBase stablish a connection with SQL
SErver using TCP/IP, everything works fine. So, if I let the connection
"sleeping", or better, if I let the connection idle for amount of time, I
need to stablish the connection to ther SQL SErver again.
I hadn't the same situation in the old instance as I having. I think that
it's happening because the other instance was dedicated to this application
and that new Instance don't.
In this new Instance I have many other connections simultaneously, about 200
processes.
Just to complete the sintomns.
To access the application, I need to logon in the application. This logon,
stablish a connection to SQL SErver and enable the interface to work.
When I let the connection idle for a little period of time (more or less - 5
minutes), I need to logon on the application again.
Anybody knows what's going on? Are there any settings to change this time-out
configuration just for a specific connections?
Thanks
Best Regards
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200709/1Hi
Does this occur for other applications on this server?
Have you changed anything on the client, other than the server name in the
connection string?
Have you tried other protocols?
Does this occur if the application is running on the server itself?
Are you using a connection pooling?
Do you have AV or ISD software running on the server?
Have you tried connecting a client into the same same hub as the server?
John
"julianohorta via SQLMonster.com" wrote:
> Hello, All!
> Good Afternoon!
> I'm having a strange situation in my SQL SErver 2000 SP3a with 4 Processors,
> 4GB of RAM and high-end disk sub-system.
> I migrate a specific database from another instance with SQL SErver 2000 SP3a
> too to this new server with more hardware resource than another one.
> The application that access this DataBase stablish a connection with SQL
> SErver using TCP/IP, everything works fine. So, if I let the connection
> "sleeping", or better, if I let the connection idle for amount of time, I
> need to stablish the connection to ther SQL SErver again.
> I hadn't the same situation in the old instance as I having. I think that
> it's happening because the other instance was dedicated to this application
> and that new Instance don't.
> In this new Instance I have many other connections simultaneously, about 200
> processes.
> Just to complete the sintomns.
> To access the application, I need to logon in the application. This logon,
> stablish a connection to SQL SErver and enable the interface to work.
> When I let the connection idle for a little period of time (more or less - 5
> minutes), I need to logon on the application again.
>
> Anybody knows what's going on? Are there any settings to change this time-out
> configuration just for a specific connections?
> Thanks
> Best Regards
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200709/1
>

Connection to SQL 2000 database with .Net 1 Application

Hi there,

Has anyone ever encountered problems making .Net applications connect to a SQL database on SQL 2000 with SP3a?

It's running on a virtual machine with a Windows Server 2000 Std with SP4, the .Net application is working with .Net Framework 1.1.4322.573.For some reason it can't connect to the SQL database using the specified username and password in the web.config file even though the user exists in the SQL database. I've tried using the SA password but this still doesn't work. I can logon to SQL Query Analyzer using the SA password but not using the other username.

The .Net application does work on other systems of mine all of which can run on Windows Server 2000 and 2003, I have compared them but can't find any differences.

Any ideas anybody?

Thanks,

Chris

I'm guessing that your SQL2000 instance is set up for Windows only logins.
In enterprise Manager right click on the server and select "properties".
In the security tab ensure that the Authentication mode is "SQL Server and Windows".