how many people can connect to the mdb
Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: General Discussion
Forum Description: General discussion and chat on any topic.
URL: https://forums.webwiz.net/forum_posts.asp?TID=12013
Printed Date: 01 April 2026 at 10:05am Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: how many people can connect to the mdb
Posted By: asp what that??
Subject: how many people can connect to the mdb
Date Posted: 01 October 2004 at 2:59pm
|
how many people can you have connected to a mdb at one time??
|
Replies:
Posted By: Mart
Date Posted: 01 October 2004 at 3:07pm
|
255 Concurrent users maxium. But performance is on a sliding scale
|
Posted By: Mart
Date Posted: 01 October 2004 at 3:09pm
|
Note: Concurrent means the number of users connected at the EXACT time,
say a query takes 1 millisecond, that would mean 255 users would have
to request the QUERY (NOT the page) at the exact same time...
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:10pm
|
that does not seem like much!!
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:11pm
|
i am looking at updating the DB alot ever few mins...and having over 1000 users updating the db between ever few sec to ever few mins
|
Posted By: Mart
Date Posted: 01 October 2004 at 3:16pm
|
For that you should consider SQL Server, it will also be tonnes better for performance.
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:17pm
|
ok...how many connects for sql?
|
Posted By: Mart
Date Posted: 01 October 2004 at 3:22pm
Heres all the limitations: (cut short - unlimited)
| |
Maximum sizes/numbers |
| Object |
SQL Server 7.0 |
SQL Server 2000 |
| Batch size |
65,536 * Network Packet Size1 |
65,536 * Network Packet Size1 |
| Bytes per sort string column |
8,000 |
8,000 |
| Bytes per text, ntext, or image column |
2 GB-2 |
2 GB-2 |
| Bytes per GROUP BY, ORDER BY |
8,060 |
8,060 |
| Bytes per index |
900 |
9002 |
| Bytes per foreign key |
900 |
900 |
| Bytes per primary key |
900 |
900 |
| Bytes per row |
8,060 |
8,060 |
| Bytes in source text of a stored procedure |
Lesser of batch size or 250 MB |
Lesser of batch size or 250 MB |
| Clustered indexes per table |
1 |
1 |
| Columns in GROUP BY, ORDER BY |
Limited only by number of bytes per GROUP BY, ORDER BY |
Limited only by number of bytes per GROUP BY, ORDER BY |
| Columns or expressions in a GROUP BY WITH CUBE or WITH ROLLUP statement |
10 |
|
| Columns per index |
16 |
16 |
| Columns per foreign key |
16 |
16 |
| Columns per primary key |
16 |
16 |
| Columns per base table |
1,024 |
1,024 |
| Columns per SELECT statement |
4,096 |
4,096 |
| Columns per INSERT statement |
1,024 |
1,024 |
| Connections per client |
Maximum value of configured connections |
Maximum value of configured connections |
| Database size |
1,048,516 TB3 |
1,048,516 TB3 |
| Databases per instance of SQL Server |
32,767 |
32,767 |
| Filegroups per database |
256 |
256 |
| Files per database |
32,767 |
32,767 |
| File size (data) |
32 TB |
32 TB |
| File size (log) |
4 TB |
32 TB |
| Foreign key table references per table |
253 |
253 |
| Identifier length (in characters) |
128 |
128 |
| Instances per computer |
N/A |
16 |
| Length of a string containing SQL statements (batch size) |
65,536 * Network packet size1 |
65,536 * Network packet size1 |
| Locks per connection |
Max. locks per server |
Max. locks per server |
| Locks per instance of SQL Server |
2,147,483,647 (static)
40% of SQL Server memory (dynamic) |
2,147,483,647 (static)
40% of SQL Server memory (dynamic) |
| Nested stored procedure levels |
32 |
32 |
| Nested subqueries |
32 |
32 |
| Nested trigger levels |
32 |
32 |
| Nonclustered indexes per table |
249 |
249 |
| Objects concurrently open in an instance of SQL Server4 |
2,147,483,647 (or available memory) |
2,147,483,647 (or available memory) |
| Objects in a database |
2,147,483,6474 |
2,147,483,6474 |
| Parameters per stored procedure |
1,024 |
2,100 |
| REFERENCES per table |
253 |
253 |
| Rows per table |
Limited by available storage |
Limited by available storage |
| Tables per database |
Limited by number of objects in a database4 |
Limited by number of objects in a database4 |
| Tables per SELECT statement |
256 |
256 |
| Triggers per table |
Limited by number of objects in a database4 |
Limited by number of objects in a database4 |
| UNIQUE indexes or constraints per table |
249 nonclustered and 1 clustered |
249 nonclustered and 1 clustered |
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:26pm
|
ok ty....i have noticed that the select statements for sql server and mdb are diff...how diff are they...and how hard would it be for me to learn...but i have a really good handle on mdb
|
Posted By: Mart
Date Posted: 01 October 2004 at 3:28pm
|
What do you mean by differant? You can use Stored Procedures but there is not a lot of differance in select statements
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:32pm
If strDatabaseType = "SQLServer" Then strSQL = "EXECUTE " & strDbProc & "AuthorDesc" Else strSQL = "SELECT " & strDbTable & "Author.Username, " & strDbTable & "Author.Author_ID " strSQL = strSQL & "FROM " & strDbTable & "Author " strSQL = strSQL & "ORDER BY " & strDbTable & "Author.Author_ID DESC;" End If
|
Posted By: Mart
Date Posted: 01 October 2004 at 3:34pm
The first statement is executing a stored procedure, if you want to use
sp's then you should really buy a sql server 2000 book. However you can
use normal select statements but sp's have performance advantages
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:35pm
|
strSQL = "select * from thistable"
that would work on sql server?
|
Posted By: dj air
Date Posted: 01 October 2004 at 3:39pm
yes. the queries you see in the forum would work on SQL server or ms access.
its when you come to stored procedures they are different.
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:40pm
|
ok good enough...thank you for your help and your time
|
Posted By: Mart
Date Posted: 01 October 2004 at 3:44pm
Queries are basically the same, apart from some extra things and dates are handled differantley.
You might want to download MSDE, a free but less powerful version of
SQL Server 2000 to experiment with, set up and download instructions
are here:
http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1 - http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1
|
Posted By: asp what that??
Date Posted: 01 October 2004 at 3:45pm
|