|
 |
access_asp thread: Limits of Access
Message #1 by "Stephen Proctor" <steveproctor@c...> on Sun, 9 Dec 2001 23:42:22
|
|
I have a general question on Access and ASP. I often read that Access is
suitable for a "small" office or "small" number of users. But I've never
heard this quantified. Approximately what is small? In my case, I have 6-
10 users in a small office. They do not use the database constantly, but
as a relatively small part of their jobs. It will probably be rare to
have two users at the same time and I think very unusual to have three or
more. But, of course, when I test my programs myself they work fine, but
I have a concern about multiple users. What are the limits of Access as a
web-based database? Thank you.
Steve
Message #2 by =?iso-8859-1?Q?Mikael_=D6stberg?= <Mikael.Ostberg@i...> on Mon, 10 Dec 2001 10:30:29 +0100
|
|
Hi Steve,
I would say that Access is very suitable for the enviroment you are
describing.
The only reason you should upgrade to SQL Server would be if you will use
very complex SQL statements that would work better in a Stored Procedure or
if you need automated data transformation or something.
In my latest project, the client did not want to pay for SQL Server, so the
entire thing is driven by Access. It's a e-commerce site with 3000 products
and 1000 members after just 40 days online. It is actually working very
fine. (www.sodersrchobby.se)
Well... That's my opinion...
::m
-----Original Message-----
From: Stephen Proctor [mailto:steveproctor@c...]
Sent: den 10 december 2001 00:42
To: Access ASP
Subject: [access_asp] Limits of Access
I have a general question on Access and ASP. I often read that Access is
suitable for a "small" office or "small" number of users. But I've never
heard this quantified. Approximately what is small? In my case, I have 6-
10 users in a small office. They do not use the database constantly, but
as a relatively small part of their jobs. It will probably be rare to
have two users at the same time and I think very unusual to have three or
more. But, of course, when I test my programs myself they work fine, but
I have a concern about multiple users. What are the limits of Access as a
web-based database? Thank you.
Steve
Message #3 by "Ed Rivis" <edrivis@b...> on Thu, 13 Dec 2001 07:59:00
|
|
Hi;
I've been wondering about what costs are involved in an upsize from Access
to SQL Server ...i.e. how do you calculate how many licenses you require
etc.? (I dont have any SQLServer experience yet but I know at some point
soon I need to get into it)
Cheers //// Ed
> Hi Steve,
>
> I would say that Access is very suitable for the enviroment you are
> describing.
>
> The only reason you should upgrade to SQL Server would be if you will use
> very complex SQL statements that would work better in a Stored Procedure
or
> if you need automated data transformation or something.
>
> In my latest project, the client did not want to pay for SQL Server, so
the
> entire thing is driven by Access. It's a e-commerce site with 3000
products
> and 1000 members after just 40 days online. It is actually working very
> fine. (www.sodersrchobby.se)
>
> Well... That's my opinion...
>
> ::m
>
> -----Original Message-----
> From: Stephen Proctor [mailto:steveproctor@c...]
> Sent: den 10 december 2001 00:42
> To: Access ASP
> Subject: [access_asp] Limits of Access
>
>
> I have a general question on Access and ASP. I often read that Access
is
> suitable for a "small" office or "small" number of users. But I've
never
> heard this quantified. Approximately what is small? In my case, I have
6-
> 10 users in a small office. They do not use the database constantly,
but
> as a relatively small part of their jobs. It will probably be rare to
> have two users at the same time and I think very unusual to have three
or
> more. But, of course, when I test my programs myself they work fine,
but
> I have a concern about multiple users. What are the limits of Access as
a
> web-based database? Thank you.
>
> Steve
Message #4 by "Ken Schaefer" <ken@a...> on Thu, 13 Dec 2001 22:25:19 +1100
|
|
Depends on your version of SQL Server. Contacting your Microsoft VAR is
probably the best idea.
IIRC
Unless you are using SQL Server on an intranet or similar where you know the
exact (or approximate) number of connecting clients then:
- for SQL Server 7 you need to buy the Internet Connector Licence
- for SQL Server 2000 you licence by processor (eg unlimited connections for
x processors - in SQL Server you can choose how many processors to let it
run on)
Cheers
Ken
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "Ed Rivis" <edrivis@b...>
Subject: [access_asp] RE: Limits of Access
: Hi;
:
: I've been wondering about what costs are involved in an upsize from Access
: to SQL Server ...i.e. how do you calculate how many licenses you require
: etc.? (I dont have any SQLServer experience yet but I know at some point
: soon I need to get into it)
:
: Cheers //// Ed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
 |