Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
MSDE allows 5 Connections. So what is a "connection?"
- Thread starter markphsd
- Start date
NoCoolHandle
Programmer
Actually MSDE will allow many more than 5 connections.. I have personally seen 100's to an MSDE database.
What you are really limited to is 5 active querys/commands
A connection is like an open phone line between a client application and your database, while an active query is the fact that on the phone line, someone is actually talking to you.
HTH
Rob
What you are really limited to is 5 active querys/commands
A connection is like an open phone line between a client application and your database, while an active query is the fact that on the phone line, someone is actually talking to you.
HTH
Rob
- Thread starter
- #3
That's kind of what I thought.
I'm still a little bit unclear, because well, so many forms are bound to tables, or queries. Does this "talking" mean that only 5 people can edit data at the same time?
I didn't ask this question blindly, I did open up about 10 Access .adp's that are connected to the same msde db and they worked. But i couldn't test it with multiple users really working in the db.
Mark P.
Bleh
I'm still a little bit unclear, because well, so many forms are bound to tables, or queries. Does this "talking" mean that only 5 people can edit data at the same time?
I didn't ask this question blindly, I did open up about 10 Access .adp's that are connected to the same msde db and they worked. But i couldn't test it with multiple users really working in the db.
Mark P.
Bleh
NoCoolHandle
Programmer
<snip>
Does this "talking" mean that only 5 people can edit data at the same time?
</snip>
YES!
And I know what you are talking about, I have an app with 48 clients that are continuiously sending records to and querying tables from.
And we have only bumped into concurrency violations when I have rebuilt indexes during a heavy period of activity..
To find out if you have a concurrency violation occouring..
Try "DBCC concurrnecyviolations" in QA and it will tell you if one (or more) occoured.
HTH
Rob
Does this "talking" mean that only 5 people can edit data at the same time?
</snip>
YES!
And I know what you are talking about, I have an app with 48 clients that are continuiously sending records to and querying tables from.
And we have only bumped into concurrency violations when I have rebuilt indexes during a heavy period of activity..
To find out if you have a concurrency violation occouring..
Try "DBCC concurrnecyviolations" in QA and it will tell you if one (or more) occoured.
HTH
Rob
- Thread starter
- #5
I somewhere read, that the MSDE is optimized for max. 5 active connections ( 5 active queries running on MSDE ), when you run more queries, the performance of MSDE will decrease.
Zhavic
---------------------------------------------------------------
In the 1960s you needed the power of two Comodore64s to get a rocket to the moon. Now you need a machine which is a vast number of times more powerful just to run the most popular GUI.
Zhavic
---------------------------------------------------------------
In the 1960s you needed the power of two Comodore64s to get a rocket to the moon. Now you need a machine which is a vast number of times more powerful just to run the most popular GUI.
- Thread starter
- #7
Yes I've read that too zhavic. But optimized for what kind of queries? They don't go into great detail. So i'm still unlcear on that, but more confident in using the MSDE for about 20 users.
There are so many conflicting reports of how many people can use MSDE now, just like how many could use an Access mdb back end and keep it stable. They say more then 10 or 15 and you should consider upsizing, yet...
I have 20 users on an AccessMDB FrontEnd/BackEnd system and read of people having about 50 or 75. For me It runs fairly stable but there are occasional corruptions. I think I would be a little more comfortable with MSDE though. Comfortable only because if the company grows I'll have some SQL Server background by that time and will be able to handle some more users.
Mark P.
Bleh
There are so many conflicting reports of how many people can use MSDE now, just like how many could use an Access mdb back end and keep it stable. They say more then 10 or 15 and you should consider upsizing, yet...
I have 20 users on an AccessMDB FrontEnd/BackEnd system and read of people having about 50 or 75. For me It runs fairly stable but there are occasional corruptions. I think I would be a little more comfortable with MSDE though. Comfortable only because if the company grows I'll have some SQL Server background by that time and will be able to handle some more users.
Mark P.
Bleh
Try to look there
This was there
Performance
MSDE 2000 is a local data engine that can be shared. It has a managed concurrency workload governor that limits up to five concurrent batch workloads for optimal performance. Commands and log entries are available to monitor instances where more than five workloads are executed concurrently, a situation that can cause slower performance even on well-tuned systems. As more batch workloads are submitted beyond the five-workload limit, the concurrency governor continues to slow down the system. These workloads are not dropped or lost; they are still processed, but in an increasingly degraded performance mode. If your solution must support more than five concurrent workloads, it is highly recommended that you migrate to SQL Server 2000 or SQL Server 2000 Enterprise Edition for optimal performance at this higher level of scalability
Zhavic
---------------------------------------------------------------
In the 1960s you needed the power of two Comodore64s to get a rocket to the moon. Now you need a machine which is a vast number of times more powerful just to run the most popular GUI.
This was there
Performance
MSDE 2000 is a local data engine that can be shared. It has a managed concurrency workload governor that limits up to five concurrent batch workloads for optimal performance. Commands and log entries are available to monitor instances where more than five workloads are executed concurrently, a situation that can cause slower performance even on well-tuned systems. As more batch workloads are submitted beyond the five-workload limit, the concurrency governor continues to slow down the system. These workloads are not dropped or lost; they are still processed, but in an increasingly degraded performance mode. If your solution must support more than five concurrent workloads, it is highly recommended that you migrate to SQL Server 2000 or SQL Server 2000 Enterprise Edition for optimal performance at this higher level of scalability
Zhavic
---------------------------------------------------------------
In the 1960s you needed the power of two Comodore64s to get a rocket to the moon. Now you need a machine which is a vast number of times more powerful just to run the most popular GUI.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question