MSDE Thread Consumption

  • Thread starter Thread starter MikeC
  • Start date Start date
M

MikeC

I'm planning to build a database using an MSDE 2000 database as the back end
and an Access XP project (ADE) as the front end. The database will be used
to maintain, schedule and report employee training classes. The front end
will also utilize Windows NT authentication. Ultimately, this application
may be migrated to SQL Server, but most likely not for another 2-3 years.

We expect to have about 50-75 users in total, but probably not more than
about 5 concurrent users.

Currently, my greatest concern is performance. I am not trying to build a
super fast database, but I want the performance to be acceptable to the
users.

I have read several KB articles, web pages and NG posts on this subject.
Some useful ideas are presented in the below link:

http://office.microsoft.com/en-us/assistance/HP030870191033.aspx

One of the recurring design themes I have found is to use views or stored
procedures instead of queries as the record sources for forms and reports.
I can certainly do this, but I sense that I'm still missing some important
information that could further help me to conserve the 5(?) concurrent TBU
threads provided by MSDE 2000.

Does anyone else have any other useful tips that I should build into the
design to best minimize thread consumption?
 
The next version of MSDE, SQL-Server Express 2005, will alleviates much of
these connection problems; if you have them in the first time with MSDE
2000.

Don't worry about performance and start practicing with MSDE.

S. L.
 
Thanks for the info. I have 2 follow up questions:

1) Will SQL-Server Express 2005 be available to Office XP users at no
additional licensing cost or must we purchase new software licenses?

2) Will SQL-Server Express 2005 be bundled with Office 2005 just as MSDE
2000 is currently bundled with Office 2002/2003?
 
Back
Top