Database suggestions

August 19, 2008 7:16 AM

Database Olympics: File Maker Pro vs. MySQL! Help us pick a database system (Anko or Firebrand). Which do you think is superior to run a print publication database?

I work for a small-sized book publisher (17 employees). We are in the process of choosing between Anko and Firebrand database systems to keep track of all aspects of publishing from acquisitions, to production, marketing, and sales. Anko works via File Maker Pro and Firebrand is web-based MySQL. Does anyone have experience with either of these programs? Any insights? Concerns?

Thanks!

posted by spakto to computers & internet (6 comments total)

FileMaker Pro doesn't really support SQL, so while it's a database, it's not what most people think of as a database. So you'll have a smaller population of people who can support it

MySQL supports most SQL (if not conspicuously well); anybody with a knowledge of SQL would be able to access the back-end, if you needed help with that.

The front-ends, in both cases are proprietary, and probably have a small population of people knowledgeable in them.

Me, I'd look for an open source CMS system, but I don't know your business or your requirements. Given only that information you've presented here, I'd say avoid FileMaker.
posted by orthogonality at 7:37 AM on August 19, 2008

Thanks. We need a database to keep track of author information, blurbs, printing schedules, prices, sales, etc. so that everyone can access it and update fields when necessary. This should do away with various inner-office memos and save a lot of time hunting down figures or schedule dates. For example, if an author moves we can update the address in one place and everyone will have the updated info.
posted by spakto at 7:48 AM on August 19, 2008

Evaluate the product (Anko or Firebrand) based on your perceived needs, not which backend they use. Demo both applications, decide what your requirements are, and pick the most economical solution that meets your needs. FileMaker pro does support SQL -- and the arguement that it is easier to manage than MySQL is not entirely true. I would not say no to Filemaker, or a MySQL solution. Many small businesses have run for years on powerful systems built on Filemaker. It is a wonderful system for small businesses that can scale out as your need increases.

Again, don't make the decision based on a Filemaker v. MySQL argument. Your backend will have little to do with how well it works in your workplace. There are horrible MySQL applications, and horrible Filemaker applications.
posted by SirStan at 8:10 AM on August 19, 2008

spakto writes "We need a database to keep track of author information, blurbs, printing schedules, prices, sales, etc. so that everyone can access it and update fields when necessary. This should do away with various inner-office memos and save a lot of time hunting down figures or schedule dates. For example, if an author moves we can update the address in one place and everyone will have the updated info."

Sounds like you could just use a wiki. Many of which are free and easy to install.
posted by orthogonality at 8:14 AM on August 19, 2008

Filemaker's non-SQL-ness doesn't really come to bear here. What's important is if either of these products meet your needs (and you can afford them).

Ask both companies for a list of clients you can contact about how they use the product, how they arrived at the decision to use that product, and how it affects their work flow. And find out about how they work: it could be similar to your work flow or wildly divergent.

Document your work flow. Figure out what you want your work flow to be. Write all these things down.

Schedule demos with both vendors. Make sure you have a long list of questions for the demo.

And find out what the 'hidden' costs are. Firebrand seems to want a Windows terminal server and SQL server (according to the vendor's site). Anko needs a server. These things add up.

And while I'd recommend open source too, a CMS is not what you're looking for. I suspect that the number of people supporting any potential open source title management software is remarkably small.
posted by jdfan at 8:16 AM on August 19, 2008 [1 favorite has favorites]

SirStan writes:

Again, don't make the decision based on a Filemaker v. MySQL argument. Your backend will have little to do with how well it works in your workplace. There are horrible MySQL applications, and horrible Filemaker applications.

I think this cuts to the very heart of the issue. The backend is far less important than how well the application itself is written and supported. You really need to demo both systems in your workplace, and spend a week or two evaluating each one in a real world setting to see which one is the more acceptable solution for your team.

FileMaker and MySQL are both very capable database environments, and both can easily handle the general tasks you are interested in performing. What really matters are ease of use, proper workflow, reliability, and, if you change your workflows a lot, flexibility. These are qualities of the application and the developer(s), not necessarily the backend.

FWIW, I am an in-house FileMaker developer for a medium-sized medical services company, and we use a variety of database applications to run our company. We use Siebel/Oracle for our big CRM tasks as it is a very robust environment, and FileMaker for our lab facility, as it is a very malleable environment. The latter is a key feature for us, as our lab systems are continuously being upgraded, and it takes us a lot less time/staff to develop our FileMaker systems. We also have a lot of back-and-forth between these environments.

My best advice would be to just spend some time with both systems you are evaluating, and see which one best meets your immediate and long-term needs. Also, speak to other companies that use each system you are considering, and make sure you understand their strengths and weaknesses. After doing all that legwork, you should be well positioned to make an informed decision. Good luck!
posted by mosk at 11:26 AM on August 19, 2008