>Cost is the primary concern. SQL Server is much more expensive than
>mySQL, albeit, it's also much easier to manage because of the toolset
>built into the application.
Tony,
Thanks for the link - alot of great information. I have a question
regarding MSDE you mentioned. You said it is limited to 5 processes and not
5 users. So is a process something like running a query, report,etc. My
database currently has about 200 users - 20 concurrent users. The size is 75
MB. Are there any tools out there that document the number of processes
running? I would love to use MSDE but I don't want my users to see a
decrease in performance. Thanks for your help.
> >Cost is the primary concern. SQL Server is much more expensive than
> >mySQL, albeit, it's also much easier to manage because of the toolset
[quoted text clipped - 14 lines]
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
Tony Toews - 10 Nov 2004 21:26 GMT
>Thanks for the link - alot of great information. I have a question
>regarding MSDE you mentioned. You said it is limited to 5 processes and not
[quoted text clipped - 3 lines]
>running? I would love to use MSDE but I don't want my users to see a
>decrease in performance. Thanks for your help.
What happens is the sixth and subsequent process have to wait thief
turn. If the processes are fast then this isn't a problem. Ten
users running long reports simultaneously would be a problem but
that's unlikely.
There is something built in that you can interrogate to see if you've
hit the throttling limits.
One person posted that he'd successfully had about a hundred users on
an MSDE system without any problems. But clearly that may be a system
which was highly optimized for SQL Server and he'd spent some
considerable time tweaking.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm