Question How many users can be log in a split DB
- Thread starter Joe8915
- Start date
It ultimately depends on what your users will be doing and the server the database is on, if all they are doing is basic data entry then you can have more than if they were running many complicated reports.
Could you give an idea of what the database is for?
Joe8915
Registered User.
- Local time
- Today, 12:47
- Joined
- Sep 9, 2002
- Messages
- 820
Dan, thanks for the quick reply.
When I converted to SQL it runs allot smoother. It’s always been a question that I had on my mind. They are running a few reports, but nothing real complicated. I have only one that would fit that category. The database is tracking invoices, and as well other items. I am tracking about 8,000 contracts any all status against those contracts. I could go on, but that should give you an idea.
When I converted to SQL it runs allot smoother. It’s always been a question that I had on my mind. They are running a few reports, but nothing real complicated. I have only one that would fit that category. The database is tracking invoices, and as well other items. I am tracking about 8,000 contracts any all status against those contracts. I could go on, but that should give you an idea.
- Local time
- Today, 13:47
- Joined
- Feb 28, 2001
- Messages
- 30,861
If the user front ends are local to each user, your limit will be strictly based on the back end version of SQL and its limits. With isolated FE files, Access is not your pacing item because it is using ODBC (probably?)
I have seen some of our own ODBC systems have over a hundred SQL back-end users - but the FE wasn't access in that case, it was a Java-based web page. Still, ODBC is ODBC regardless of who runs it. Your pacing item will be the resources that were made available to the SQL server code. Small machine? Few users. Larger machine? More users. It's that simple.
I have seen some of our own ODBC systems have over a hundred SQL back-end users - but the FE wasn't access in that case, it was a Java-based web page. Still, ODBC is ODBC regardless of who runs it. Your pacing item will be the resources that were made available to the SQL server code. Small machine? Few users. Larger machine? More users. It's that simple.
boblarson
Smeghead
- Local time
- Today, 11:47
- Joined
- Jan 12, 2001
- Messages
- 32,053
Doc has it. With an Access backend, it is like GaryPanic said. But with SQL Server it really only has to do with
1. Your licensing of SQL Server (depending on which version you are using it could be limited to certain number of seats unless you have a per processor license).
2. Your network infrastructure as to whether it can handle the traffic.
1. Your licensing of SQL Server (depending on which version you are using it could be limited to certain number of seats unless you have a per processor license).
2. Your network infrastructure as to whether it can handle the traffic.
