|
|
Posted by David Portas on 10/02/40 11:55
Jim Devenish wrote:
> We are trying to evaluate the use of SQL Server as a back-end and
> although the system works with a very small number of users we are
> encountering difficulties when the number rises to about 8-10. If we
> cannot overcome these we will revert to Access back-end.
>
> If we are successful, the licenses will be acquired for Enterprise
> edition. There is no intention of violating licences. We do however
> wish to test the system fully before advancing.
>
> As I said in my original post, I am happy to explore the problem in
> another post. I just wanted to eliminate the possibility that the use
> of the Developer version was contributing to the problem.
>
SQL Server can easily handle thousands of simultaneous users. But it's
equally true that poor design and implementation can kill performance
even in a small database with a handful of users.
Did you review and redesign the logical and physical data model when
you ported to SQL Server? Did you rewrite your data access code to run
as server-side T-SQL stored procedures? If you did not do those things
or if you are still binding tables to Access forms then you are not
taking good advantage of SQL Server and N-tier architecture. Do not
expect SQL Server to be a supercharged version of Jet - it just isn't.
Assuming you have put in the effort to re-architect for SQL Server then
take a look at the following article for suggestions on troubleshooting
performance issues. These are primarily tuning and troubleshooting
suggestions. They are not a substitute for effective design up-front.
http://support.microsoft.com/?id=298475
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|