[AccessD] SQL and Access

...no :)

William

----- Original Message ----- 
From: <DWUTKA at marlow.com>
To: <accessd at databaseadvisors.com>
Sent: Sunday, June 18, 2006 8:37 PM
Subject: Re: [AccessD] SQL and Access


> Your kidding right?  An .mdb on the local web server will put a SQL server
> to shame until you get to MAJOR traffic, and even then, the webserver is 
> the
> limit.  The only drawback to a local .mdb is that it doesn't have 
> redundancy
> like a SQL server.
>
> Drew
>
> -----Original Message-----
> From: William Hindman [mailto:wdhindman at dejpolsystems.com]
> Sent: Saturday, June 17, 2006 5:35 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] SQL and Access
>
> ...depends on their transaction level on the site ...an mdb is limited to 
> ~1
>
> transaction per second or maybe 20 site users (given that they're not all
> hitting the submit button at the same time) ...anything above that traffic
> level would need SQL Server or equivalent ...imnsho :)
>
> ...in-house, less than 20-25 db users and they're ok with an mdb assuming
> its decently designed ...more than 25 and its time to step up ...in actual
> practice I put clients with anything more than 3 users on Small Business
> Server with mdb be's and start moving them to SQL Server at 11 users or
> above.
>
> ...but the administration of any client-server db is significantly more 
> time
>
> intensive than an mdb and is a major consideration when working with 
> smaller
>
> clients ...if they don't have a potential dba in-house, I certainly don't
> want to be burdened with that type of work any more than necessary ...and
> I'll keep them on an mdb much longer than otherwise.
>
> William
>
> ----- Original Message ----- 
> From: <DWUTKA at marlow.com>
> To: <accessd at databaseadvisors.com>
> Sent: Saturday, June 17, 2006 5:28 PM
> Subject: Re: [AccessD] SQL and Access
>
>
>> Do they already have SQL Server?  If not, why not just stick with an
>> Access
>> .mdb backend?
>>
>> Drew
>>
>> -----Original Message-----
>> From: Kath Pelletti [mailto:kp at sdsonline.net]
>> Sent: Friday, June 16, 2006 3:14 AM
>> To: Access D Normal List
>> Subject: [AccessD] SQL and Access
>>
>> Hi everyone -
>>
>> Can I pick your brains? I have a client who needs to put some data on the
>> web which will connect to a 3rd party shopping cart product, ie. they 
>> want
>> to display their goods on the web and allow them to be sold on to retail
>> clients. They already have the shopping cart side organised, but they 
>> have
>
>> a
>> statically typed website - no database to feed it.
>>
>> They also need an internal system which will meet administration,
>> management
>> and reporting requirements - but fairly simple stuff. They are very
>> strapped
>> for cash (smirk) and want a fairly inexpensive solution. Lately I have
>> been
>> working on .net with SQL Server 2005 systems which would be a great
>> solution
>> - but way too expensive in development costs.
>>
>> So what about SQL Server BE with Access front end? I know it's very 
>> common
>> but can someone tell me:
>>
>> - any gotchas
>> - cost for client in terms of licences they would need for SQL? I can't
>> seem
>> to find a clear answer by googling.
>>
>>
>> Thanks.
>>
>> ______________________________________
>> Kath Pelletti
>> Software Design and Solutions Pty Ltd.
>> Ph: 9505-6714
>> Fax: 9505-6430
>> Email: KP at SDSOnline.net
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>
>
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>