hog Posted March 28, 2003 Posted March 28, 2003 What is the best/most effcient method to develop an application to a backend database. Currently I have developing using Windows Application using ADO.NET to connect to an Access2002 mdb file residing on a file server running Server2000. Which is better and why? My setup described above? My setup decribed above but using a WEB application instead? Using MSDE? I have no control over having SQL Server installed on our local server and have no knowledge of it anyway. Any guidance would be greatly recieved. Oh also is there any way to optimise the accessing of an mdb file? Quote My website
wyrd Posted March 28, 2003 Posted March 28, 2003 Access is perfectly fine for a "small" business. However you'll want to change to MS SQL eventually (MSDE will work fine for development). It's much more efficient to use for larger apps. Also the .NET framework offers a specialized namespace just for the SQL Server (rather then using OleDb), which is made to take advantage of SQL Server and give you faster programs overall. Quote Gamer extraordinaire. Programmer wannabe.
*Gurus* Derek Stone Posted April 1, 2003 *Gurus* Posted April 1, 2003 If you expect to have more than one user accessing the database concurrently I strongly suggest you use MS SQL Server. I've used Access in a multi-user environment, and it isn't pretty. Start with MSDE, there's no excuse not to. Quote Posting Guidelines
hog Posted April 2, 2003 Author Posted April 2, 2003 OK, pardon my ignorance :-( but... With MSDE isn't there a limit to how many users you have running it as opposed to SQL Server. Also is it the same as Access whereby the MSDE database just resides on a file server and my application looks after everything else? Quote My website
a_jam_sandwich Posted April 2, 2003 Posted April 2, 2003 No limit to users but said that the connection degrads after 5+ users connected Not tested though Andy Quote Code today gone tomorrow!
hog Posted April 2, 2003 Author Posted April 2, 2003 Derek you say Access is naff in multi user? I have a application I wrote in Access97, 390MB and accessed by 30+ users with no bother? It is however readonly so that may make a difference?? Quote My website
hog Posted April 2, 2003 Author Posted April 2, 2003 a_jam, this is what I found re msde: MSDE 2000 is a local data engine that can be shared. It has a managed concurrency workload governor that limits up to five concurrent batch workloads for optimal performance. Commands and log entries are available to monitor instances where more than five workloads are executed concurrently, a situation that can cause slower performance even on well-tuned systems. As more batch workloads are submitted beyond the five-workload limit, the concurrency governor continues to slow down the system. These workloads are not dropped or lost; they are still processed, but in an increasingly degraded performance mode. If your solution must support more than five concurrent workloads, it is highly recommended that you migrate to SQL Server 2000 or SQL Server 2000 Enterprise Edition for optimal performance at this higher level of scalability. Quote My website
Moderators Robby Posted April 2, 2003 Moderators Posted April 2, 2003 Derek said "Start with MSDE, there's no excuse not to" This means during development and maybe QA, not for production. Quote Visit...Bassic Software
*Gurus* Derek Stone Posted April 3, 2003 *Gurus* Posted April 3, 2003 Derek you say Access is naff in multi user? I have a application I wrote in Access97, 390MB and accessed by 30+ users with no bother? It is however readonly so that may make a difference??A database that isn't written to is fairly uncommon, but yes, Access can handle reads far better than writes. Quote Posting Guidelines
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.