Re: SQL Server 200 Developer vs Enterprise versions

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.


Erland Sommarskog wrote:
Jim Devenish (internet.shopping@xxxxxxxxxx) writes:
I am having some problems in the process of moving an Access back-end
to an SQL Server back-end. Everything works but there are severe
problems of response times when the number of users builds up.

At present we are using the Developer version before committing to the
Enterprise version. BOL (quoted below) seems to suggest that, apart
from licensing, they are the same.

Can anyone please confirm that this is so. If not, what is the
difference?

The difference is exactly in the license. And when you mention users
building up, I get a little vervous that you are violating it...



--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

.

Relevant Pages

  • Re: Pros and Cons of SQL v/s MDB
    ... do you know of a backup system that can be ... >that can have over 100 users on the same back-end. ... >Now, up-sizing to SQL server is often, bu not always the ... >>After the last corruption, which was recovered by ...
    (microsoft.public.access.adp.sqlserver)
  • Re: A97 to SQL?
    ... You could migrate your data to a SQL-Server back-end, and link to your data there. ... You might have to redevelop portions of your front-end to work better with SQL-Server data. ... I am starting to wonder whether the time has come to move to something bigger, like SQL server. ... Currently I am regularly adding little enhancements, new reports, etc etc, to the A97 mdb FE, and it's very useful that I can do this. ...
    (microsoft.public.access.conversion)
  • Re: Logging queries against a .mdb
    ... If you could somehow use an ODBC driver to access the back-end, ... back-end with one that has linked tables to SQL Server tables, ... is there a way to log queries (SELECT, ...
    (comp.databases.ms-access)
  • Re: Pros and Cons of SQL v/s MDB
    ... With 20 to 30 users at its peak, Access with a shared JET back-end is not ... a SQL Server back-end can be a good option. ... and run periodic queries to update the OLAP system. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Processpr Licensing
    ... I think that with clustering, you do not have the "backup" SQL Server started, hence you only need ... and you do nee two licenses. ...
    (microsoft.public.sqlserver.setup)