DB for Small Business Environment

If you're just looking for an easy-to-use, desktop-only DB, that you really don't need a dedicated programmer to use, I'd go with Access or something similar. Access DB's could be shared and accomodate 3 or so users simultaneously, but it's really meant to be a single-user app.

There are many other alternatives, which one is the best depends on the following questions:
-How many users will be accessing the database at the same time?
-Do you plan to have a developer on staff or contracted to create the actual business app?
-What development tools will you be using to create the applications that access it?
-Do you have any special requirements?

I would check out Alpha 5 from AlphaSoftware (www.alphasoftware.com)

I have used a bunch of database products including dbase 3+, foxpro, access, etc.. and I highly recommend you try out this software. It is extremely powerful and easy to use.
You can find more testimonials on their web site.

Victor...

Depends a lot on how much "data" you are going to want to collect and what you want to do with it after its stored.
I use MySQL because its free and pretty flexible.
However, Microsoft Access could also be a contender.
I teach some database theory and these are the two that I use in my class.

The size and number of users are the main deciding factors that you need to consider.

An Jet (Access) MDB has proven to be a very good choice for a local database, and is well accepted. If used locally, and of course if the database queries are optimized, a size less than 1GB will not be that much of a factor. (A '2000 Jet mdb can hold up to 2GB of data, but because Jet databases can be linked to each other, the size is actually only limited to the amount of local resources).
On a server, with multi-users, a Jet Mdb works also well below 5 simultaneous users, but, if the database has little data (under 50Mb), it will work well with alot more users.

MSDE is also a good choice, but only for 5 or less users and up to 2GB of data.
This is very similar to SQL Server, and if you decide to change the database to SQL Server for a certain customer, it can be done in a snap, with basically no code changes in the executable.

A word about concurrent/simultaneous users:
When considering concurrent/simultaneous, do not the just calculate the potential users. The number of actual users who are trying to access the same data in a database at the same time is probably far less than the number of potential users. Consider using a factor of something like 30-50% of potential users as being actual concurrent/simultaneous users.

The real answer to your question lies in your staff.

Do you have someone who can develop an application for your specific "data tracking" needs? If so, what are they familiar with?

Are you going to hire temporary consulting help to develop andmaintain the application(s)? If so, what do they suggest as their preferred platform?

So the best answer in my opinion is MySQL, but my point is that you need to go with what the people who can produce say.

I use MySQL on a Linux box running Apache and I use PHP to develop middleware objects. It's a great solution for us.

In my consulting, I've found FileMaker Pro to be an amazing product for small and medium size businesses. It is easy for a relative novice to set up a useful database. Networking several computers to one database is only as complicated as checking the "share this database" option.

The basic version also allows you to web-enable your database if you have a dedicated internet line. Again, at it's simplest it is a matter of checking a few boxes. You can also get quite sophisticated by writing custom HTML pages that interact with your database.

However, the base version limits internet access to 10 users per 24-hour period. If your needs go beyond that you can jump to the "unlimited" version which supports as many concurrent users as your hardware can handle.

Frankly, Filemaker puts Access to shame in terms of ease of use, ease of networking, and web integration. There are various SQL options that range from free on up, but they don't offer the ease of use you probably need either.

Finally, Filemaker has a well-developed support community both online and via consultants. If you can't quite get things set up the way you want, help is easy to come by.

Best of luck with your project...

In my experience, there are no "easy to use user friendly" database applications for small business, except thouroughly tested PIM's (personal information managers) such as ACT, Goldmine, Maximizer, etc.. These data managers have numerous user defined fields and screens.

If one has an application that can't be bought off the shelf, then a professional programmer needs to write it and they should choose the right language. My programmer loves visual basic with a space delimited text file for a data format. Maybe the questions should be how do I choose a programmer?

The major problem with small business is they don't know what they need at the get go. With The flexibility of Access you can add tables as they need them, just remember the first rule in db design is create plenty of tables. The small business needs to be on a network with the db on the administrators box. Using VB you create limited use GUIs for the different users. For example: the receptionist can view files only, that way the receptionist only needs to know how to scroll the list and or print envelopes.
There are a lot of folks out there which can set this up for small business at a reasonable price and even upgrade the db remotely.

I would recommend Sybase's ASA (Adapive Server Anywhere (formerly SQLAnyWhere). This is an industrial strength DBMS. Easy to install on most popular O/S's and costs a fraction of what Oracle, Informix, IBM, etc would charge. This a fully ANSI complinant DBMS and can accomodate from 1 to 100 concurrent users easily (even more if you want to thow more hardware at it!).
You can also use most of today's popular development tools with it.
I have used it for over 8 years now. It also runs on PDA's as well (10++ in my book).

MySQL or Posgresql: Both databases are robust, fast, easy to use.

Why don't give it a try?

MS Access 2000 includes VBA(VB)6. In my experience developing bussiness applications it is the best choice. If you have MS Office 2000 premium on your desktop there is no additional expense for software. If you don't have a programmer in house there are a multitude of experienced programmers available at reasonable cost. Access also has a worldwide support community in excess of 7000 available, 24/7, free. Access provides multi-users, 2 Gb size (that's a lot of data), easy development, easy changes, and easy migration to industrial strength MS SQL as your business grows. And you don't need a super PC to run Access. If you want more information and analysis of your business needs, contact me.

Cheers,
Henry

form the reliability and continued requirement in the future go for Oracle or SQL.

i tend to agree that you can't beat access on the front end development time, but for more than 2 or 3 concurrent users I would recomend an oracle, SQL Server or even MySQL backend. You can manage Queries and such in the Access if you like, but can't beat the speed and efficiency of a real RDB server on the backend. I use SQL Server and Access for fast application development. It has worked beautifully. I leave user access to the RDB server. If you have any questions contact me. I'll be more than happy to help you with the design even for FREE. Posting answers to some of the questions here would help a ton.

If you're not ready to pay the $$ to acquire SQL Server, check out Visual Foxpro (Microsoft). True Object-oriented programming with an extrememly fast, robust database included (puts Access to shame, and if VB were a database language, it would have a database). Best part, create a stand-alone, multi-user executable of your app and distribute it wherever you want. Or use VFP as a front end to SQL Server or Oracle and gain all the advantages of the language, plus web-services. Worth checkingout...

The choice of database depends highly on your company and the application you want to use it for. For small businesses MSDE can provide a good, cost effective solution. This gives a clear and easy path if the needs of your application expand. It also means that if a customer already has SQL Server they can take full advantage of it without requiring changes to your application.

Why Notes/Domino R6 for Web & Desktop users ?

1. It's scalable to your hardware. Many OS options.
2. Years ahead of Microsoft VB.NET/Access.
3. Less server pieces to maintain than Microsoft.
4. Large community of experience on the web.
5. e-mail options & many workflow, discussion templates included...

http://www.NOTES.net
http://www.SearchDomino.com

contact us if we can be assistance over email, phone or at your site... ( reasonable. )

CLPs. Certified Lotus Professionals
http://www.prodatacorp.com
Progressive Data Corp
tech320@prodatacorp.com
708-216-9710

I am listing some choices for Windows platform. Also, I am assuming that you require data access programmatically.

If you are looking at single user (at a time), no transaction support and simple data, even an EXCEL may do. You can access it programmatically.

If you are looking at some sophistication, MS Access is a good choice. You need to invest in MS Access for the developer but the resultant MDB (database file name) and the code to access it can be distributed free. MS Access can be asimple backend database or can be a full fledged front end also.

If the need is expected to grow, you may use MSDE. This is a free database having all the features of MS SQL Server (with some limitations on sizes etc.) but without a front end to administer. (But, I am sure you can find some freeware for this purpose). This is really between ACCESS and SQLServer and when you are ready, the migration to MS SQL Server is very easy.

My first pick is Oracle, but it is pricey and overkill for desktop jobs. It is very portable, has a huge user base, is probably the most robust and extensible dbase on the market. There are modules for almost any added, not out-of-box functionality.

DB2 is very solid, performance has picked up, and the price points have improved markedly. It can run just about anywhere and scales almost as exremely as Oracle.

SQL Server is a strong pick, but only is you are run in Windows. Performanceis excellent, but scalability and flexibility is weak compared to Oracle.

mySQL is free, fast and portable, but doesn't have all the robustness, SQL compliance of the comercail products. It is also not a true relationsal DB, but a high-end ISAM database. Stored procedures ahould be added as part of the product by version 4.1. This, combined with fuller SQL compliance and support for come complex SQL statments will make this an even more competative product than it already is, and it is already a well accepted tool in comercial and production environments.

If you jut need a destop Windows based database, Access/Jet is wonderful, but don't forget Adabas.

I started with dBase and have had an opportunity to work with many of the products mentioned, including Notes/Domino (which I really enjoyed, although I don't really think of it as a relational database). All have their good and bad points, but let's get real here. Oracle or SQLServer for 5 users? A lot of small databases are created using Access -- love it or hate it -- simply because the customer already owns it and cannot afford anything more, or a programmer to create a front end for something more powerful like MySQL. Many of my customers started very small with Access databases they struggled to piece together themselves using wizards and "Databases for Dummies" books. These got them through until they had a better idea of what they wanted and could afford to pay someone to create something more polished and powerful.

For what you need, just one word :

FileMakerPro.

Go for it and enjoy.

Happy FileMaking

JW

In selecting your DBMS, look carefully at all the requirements, external as well as internal. All interested and concerned individuals/entities are stakeholders. A SB DBMS should include these. For example, your bank. If your business model includeson-line payments, then your bank is a vital stakeholder whose own requirements your DBMS should support. Your business model should determine your SB DBMS requirements. Don't work backwards from vendor/product promotions.