Hello! Thanks for the video! I followed carefully the steps mentioned here and on the other video you posted called "Connect and query data from Microsoft SQL Server to FlutterFlow". I was able to complete all steps until the Step 3 of this video and the equivalent moment of the other video I mentioned. However the data is not appearing in the table, list view or even other options to see the data on my app project. It seems, at least from my perspective, that some information is missing or in need to be updated... Would you have a channel to provide support on a situation like that?
Hello and thanks for your question Hard to compare in details as I have limited experience with Firebase and 15+ years with SQL Server (and years with Azure). But as I see from our and ours customers current experience - to have ability connect external database to FlutterFlow (sometimes db is legacy or from products that use SQL Server internally), some additional control over hosting and flexibility of scripts is always a plus. I see Firebase more as "ready-to-use" backend with own internal logic, "rules" and limitations that come from its purpose. Current ApiFlow focus is to provide ability to connect other datasources, without strict requirement to use Firebase or Supabase only. If compare Firebase to SQL Server as technologies - definitely full-featured RDBMS like SQL Server is much more scalable and efficient when it comes to hi-load but for small projects you will not see big difference. Again everything comes in price and RDBMS requires good data architecture and is less flexible in schema changes. So if you are making small app for limited usecase - Firebase will be fast to start and easy to support. But if you working on unique product that can require scale, complex data logic or ability to integrate other software, change hosting provider or move to bare metal - better to use "classic" storages like SQL Server, PostgreSQL, or MongoDB.
Hello!
Thanks for the video!
I followed carefully the steps mentioned here and on the other video you posted called "Connect and query data from Microsoft SQL Server to FlutterFlow".
I was able to complete all steps until the Step 3 of this video and the equivalent moment of the other video I mentioned. However the data is not appearing in the table, list view or even other options to see the data on my app project. It seems, at least from my perspective, that some information is missing or in need to be updated...
Would you have a channel to provide support on a situation like that?
Hello
Thanks for your request
Please, reach us via chat at APIxFlow site and we will gladly help to continue setup
How could this be better than using Firebase? As I'm thinking of using Azure in future!
Thank you
Hello and thanks for your question
Hard to compare in details as I have limited experience with Firebase and 15+ years with SQL Server (and years with Azure). But as I see from our and ours customers current experience - to have ability connect external database to FlutterFlow (sometimes db is legacy or from products that use SQL Server internally), some additional control over hosting and flexibility of scripts is always a plus. I see Firebase more as "ready-to-use" backend with own internal logic, "rules" and limitations that come from its purpose. Current ApiFlow focus is to provide ability to connect other datasources, without strict requirement to use Firebase or Supabase only.
If compare Firebase to SQL Server as technologies - definitely full-featured RDBMS like SQL Server is much more scalable and efficient when it comes to hi-load but for small projects you will not see big difference. Again everything comes in price and RDBMS requires good data architecture and is less flexible in schema changes.
So if you are making small app for limited usecase - Firebase will be fast to start and easy to support.
But if you working on unique product that can require scale, complex data logic or ability to integrate other software, change hosting provider or move to bare metal - better to use "classic" storages like SQL Server, PostgreSQL, or MongoDB.