Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sql777
Constraint Violating Yak Guru
314 Posts |
 Posted - 2004-03-31 : 13:22:35
|
| Hi,Let me give you a scenerio. If I was to use a Access database for a Forums Application, at what point (row count) do you think it would become a serious performance problem? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-31 : 13:24:09
|
| http://www.4tops.com/ms_access_tips/ms_access_limitations.htmTara |
 |
|
|
sql777
Constraint Violating Yak Guru
314 Posts |
Posted - 2004-03-31 : 13:29:41
|
| ok so a table can be 1 GIG!But much will performance degrade after that? Anyhow, realistically that table might have 100 000 rows, or 20 000 in one table and 80 000 in another table.anyone have such a access db that works fine?Is there indexing options also? |
|
|
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2004-03-31 : 14:55:14
|
| it's not so much row count as it is concurrency. Access is actually quite efficient when it comes to accessing tables, even accross networks, if a table is indexed sufficiently. So the key is concurrency, since Access is limited by the windows filesystem as to how much of a file it can lock, and how it can update it, etc -- unlike in SQL server, in which 1 single process ultimately can control when to write to the disk. In Access, each process is fighting to read/write on it's own and that is what causes corruption and slow downs. In fact, that is probably the single biggest difference between the JET engine and SQL Server: a file-sharing database engine vs. a server database engine.- Jeff |
|
|
|
|
|
|
access and row count max?