Access database error

starting to think about sql server

[macrost]

/index.asp?p=yes¦5¦80040e4d¦[microsoft][odbc_microsoft_access_driver]_too_many_client_tasks.
This just came through on my stat server.... sounds like access is starting to break eh?
Any thoughts?

Mac

[txbakers]

Yes, Access is not designed to be a web database. it can't handle the traffic.

SQL Server or mySql will work. You need a real database server.

[macrost]

txbakers,
That's what I figured. However there were only 2 active users on at that time, and this is the first time I have seen it. I only get about 1500 uniques a week. At the most I have seen was 10 uniques at a time.

Mac

[txbakers]

My site was brought to a halt when I reached 10 active connections. I spent a looooong weekend upgrading everything.

[macrost]

Gotcha, I'm going to have to get the extra 35 bucks a year for sql server. Not to bad in my mind.

Mac

[wackal]

are you using an odbc connection to your database? you might want to try using a dsn-less connection. You'll get better performance that way.

[macrost]

Really? I always was under the impression that a dsn connection is faster and can handle more. I will try the dsn-less conn.
Thanks!
Mac

[txbakers]

yes dsn-less is generally faster, but still, get rid of Access.

[mattur]

oledb is better than odbc in a connection string, too. Note that it's not the number of unique visitors which is the limiting factor. Scaleability issues arise when two or more try to update the database at the same time.

[sullen]

Just to save you from pulling your hair out later -

dsn-less connections may be faster, but with Win2000 you get an occasional error with them which reports itself as an "unspecified error". It's highly annoying, it goes away of its own accord and then comes back again, and the only thing that fixes them is a dsn.

Or have they fixed this now?

[davemarks]

I use dns less connections all the time and never had a problem like this...

[macrost]

This is the first time that I have ever seen this before with any of my sites. The environment that I'm is a virtual server with at the most 250 sites.

Mac

[wackal]

oledb is much more stable and efficient than odbc. You should try to never use odbc if possible. also, you might want to look at you recordset code and see if you can optimize it to reduce the amount of time you are accessing the database in your pages.

From the traffic stats you entered, I don't think you need to upgrade to SQL Server. The traffic you're geting is still low and your code can definitely be optimized.