App_Data vs SQLEXPRESS performance?

Hi all,

Just wondering if there are any performance differences with having your database file in the App_Data folder vs having it directly on SQLEXPRESS.

Cheers,

Simon

Yes, but not much of one in most cases. If it's in App_Data with an autoattach, the database will be attached when it first accessed, which will delay the first request slightly. It will then stay attached for subsequent accesses. Eventually if there are no more accesses, the system will unattach it to conserve resources, I think it's between 5 and 30 minutes, but could be wrong.

In any case, the performance difference is slight, and the auto attaching and unattaching will help free memory and resources for the other applications that may be running on that server when the database isn't being used. Extremely nice for both infrequent database applications (Low resources), and high usage database applications (Since the database will always stay attached).

|||Great thanks for the detailed reply Motley! I think I'll migrate my db into the App_Data folder now =)

Cheers

App server unable to connect to SQL Server 2000 developer edition on localhost.

Anyone encounter differences between SQL2K EE and SQL2K Dev Editon?

FAILS
--
Machine_A [App Server] <-- JDBC --> Machine_A\SQL2K_Dev_Ed..db

Error: "com.inet.tds.SQLException: Connection refused"

When app server on Machine_A attempts to connect to database on
Machine_A the conenction is refused.

SUCCEEDS
---
Machine_A [App Server] <-- JDBC --> Machine_B\SQL2K_EE..db

When app server on Machine_A attempts to connect to database on
Machine_B the conenction succeeds and the app server runs normally.

JDBC driver: com.inet.tds.TdsDriver

jdbc:inetdae7:locahost:1433

I don't believe the app server is exhausting the 10-connection max on
SQL2K developer edition (there is a 10-connection limit imposed on the
developer edition, correct?)

LBlbunet@.hotmail.com (LB) wrote in message news:<35e1fa55.0404062027.3635b8b9@.posting.google.com>...
> Anyone encounter differences between SQL2K EE and SQL2K Dev Editon?
> FAILS
> --
> Machine_A [App Server] <-- JDBC --> Machine_A\SQL2K_Dev_Ed..db
> Error: "com.inet.tds.SQLException: Connection refused"
> When app server on Machine_A attempts to connect to database on
> Machine_A the conenction is refused.
>
> SUCCEEDS
> ---
> Machine_A [App Server] <-- JDBC --> Machine_B\SQL2K_EE..db
>
> When app server on Machine_A attempts to connect to database on
> Machine_B the conenction succeeds and the app server runs normally.
> JDBC driver: com.inet.tds.TdsDriver
> jdbc:inetdae7:locahost:1433
> I don't believe the app server is exhausting the 10-connection max on
> SQL2K developer edition (there is a 10-connection limit imposed on the
> developer edition, correct?)
> LB

There is no connection limit in Developer Edition - it's Enterprise
Edition with a different licence.

I don't know exactly what "Connection refused" means, but you might
want to check the SQL Server logs for failed logins, and also test
your username/password combination with osql.exe or whatever, just to
make sure it works correctly. You could also check the authentication
modes on the two servers (Windows or Mixed), to see if they are the
same - username/password works only in Mixed mode, if that's what
you're using.

Simon|||sql@.hayes.ch (Simon Hayes) wrote in message news:<60cd0137.0404070120.39c31661@.posting.google.com>...

... [See first post for text that appeared here]

> There is no connection limit in Developer Edition - it's Enterprise
> Edition with a different licence.
> I don't know exactly what "Connection refused" means, but you might
> want to check the SQL Server logs for failed logins, and also test
> your username/password combination with osql.exe or whatever, just to
> make sure it works correctly. You could also check the authentication
> modes on the two servers (Windows or Mixed), to see if they are the
> same - username/password works only in Mixed mode, if that's what
> you're using.
> Simon

Thanks for the feedback.

LB