what flavor of SQL back-end database: MS SQL Server, MySQL,...?
The comparison on just tech specs is going to be irrelevant. FM is an integrated platform offering all 3 layers of creating a solution:
1- the UI
2- the business logic / scripting
3- the database backend
The big SQL back-ends are only #3 and you have to bring your own choice of technologies for #1 (browser, application,...) and #2 (PHP, .NET, ruby, java,...)
Isolating #3 is a losing battle, FM is never going to compete with the SQL backends and has never pretended to want to.
They’re comparing to both MySQL and MS SQL Server. This is a smallish group of 40-60 users on LAN with some VPN connectivity occasionally. Cross-Platform. IT is concerned that FileMaker may not support them long-term for their needs and scalability and, of course, IT is trying to make it a case to abandon FileMaker.
Of course they are! They have never seen the famous Bubble Chart at a FileMaker Developer's Conference opening.
What Wim said about dbs and the SQL being only PART of what is needed.
But you also need to throw in that famous "Work Group" target audience for FM. And what can be done by the WG, that doesn't require IT support at all.
The point is that SQL dbs and FM can work together depending on the needs.
Thanks! Yes, they’ve been using FM successfully for years and now IT is “nervous” about the fact that the developers don’t need their support. It’s political, but trying to arm them with corporate literature and data so they feel warm and fuszzy….
If you Google "FileMaker vs MySQL" you will find some info
But it all depends
If scalability means hundreds, then MySQL wins, but with 50 to 100 users FileMaker is OK
If you need to crunch numbers ( multiple calculations over 100K records ) then MySQL wins again, by far. Try it ( FileMaker is primarily text based )
But Developing fast and cheap, FileMaker wins
> they’ve been using FM successfully for years and now IT is “nervous”