Main > Everything Else
Small Business, Why have a SQL database?
MonMotha:
If you really do need to store user account information for your users, what you probably want is LDAP, not SQL. If you're a Microsoft shop, that means Active Directory. If you're an "anything else" shop, probably OpenLDAP or Apache Directory Server. Apple has (or had, when they sold the xserve) a solution that was a rather decent frontend to OpenLDAP, IIRC. People commonly store host (PC) information in LDAP, too, since it's convenient and provides a decent way to associate users with the hosts the operate.
As for your time tracking and work order tracking, it sounds like what you probably want is a ticketing system with a time tracker built in, or maybe just a plain ol' time tracker. Check out Redmine/Chili Project for the former. For the latter, there's tons of little options that are free. These will generally use an SQL (of some sort) backend, but you won't have to do much other than set it up.
ahofle:
Minor semantic/wording correction. You wouldn't move to "SQL", you would be moving to a relational database (SQL is a language used for querying data in that relational database).
My 2 cents, stick with your spreadsheets, especially if you are unfamiliar with databases.
From what little you've revealed about your business, it doesn't sound like you have a need for complex relationships (like products, orders, customers, etc). The time to think about moving toward a true database would be when you find yourself unsuccessfully attempting to perform queries across multiple spreadsheets and failing to get the answer you are looking for from your data.
EDIT: I missed MonMotha's reply, which was basically the same as what I said. :-[
Navigation
[0] Message Index
[*] Previous page
Go to full version