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 |
sbt1
Yak Posting Veteran
89 Posts |
Posted - 2003-05-30 : 06:58:14
|
We're using MSDE as our database engine in an office with less than 10 users for this particular application.So far, it seems to be working fine.But I understand MSDE has a built-in throttling mechanism to restrict the number of concurrent connections or operations to some number (5?).Is there a way to monitor to see if we're hitting that limit and how often, so I can forecase whether we should plan to upgrade to SQL Server? |
|
JustinBigelow
SQL Gigolo
1157 Posts |
Posted - 2003-05-30 : 11:27:34
|
Using SQL Profiler you can monitor the ExistingConnection connection class to get a count. It's part of the Session event class. Check BOL for more info.hth,Justin"Contrary to its syntax GETDATE() still leaves you alone on Friday night." |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2003-05-30 : 11:58:27
|
I believe that it writes stuff into the event log when you go over the limit. It tells you how far you went over the limit as well. It's a bit cryptic how it tells you, but it will give you some idea as to how far over you are going.Michael<Yoda>Use the Search page you must. Find the answer you will.</Yoda> |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2003-05-30 : 15:43:37
|
Check out DBCC CONCURRENCYVIOLATION command in BOL. It will allow you to view the number of times you've hit the limit, and it will also allow you to log concurrency violations in the errorlog. |
|
|
|
|
|