Research and Development Project Manager at Sixense Monitoring
Real User
Top 20
2024-11-11T16:09:05Z
Nov 11, 2024
We would like to improve the management of very large databases. We have databases up to three or four terabytes, and it's not so easy to manage such large databases.
Chapter Lead at a financial services firm with 201-500 employees
Real User
Top 5
2024-03-19T12:23:10Z
Mar 19, 2024
Firebird SQL's performance has slowed since Firebird SQL 3 or 3.5 versions, where they developed over-the-wire encryption. I wouldn't recommend the solution to others for performance. The solution should add some monitoring features for the database. Firebird SQL should add the just-in-time dumps and journaling feature if it doesn't already have them.
Database sharing is a capability that Firebird SQL lacks. With database sharing, we can split the database into different machines. Database sharing is a functionality I would like to see in the solution, especially when implementing it at very large sites.
It would be nice to have a graphical user interface to handle the product. A lot of databases have it. I don't think Firebird has it. I use the ISQL directly. It's fine for me. However, it takes a while when you're creating databases and stuff. It would be helpful.
Technical support and performance could be better. We have some problems with this solution, but we don't know if the problem is with the database or the configuration. For example, sometimes, the users can't access the database.
The solution could improve by providing partitioning and encryption. It is not at the higher level of database solution but it could be with some upgrades.
Co-founder at a tech services company with 51-200 employees
Real User
2021-03-11T09:22:14Z
Mar 11, 2021
There aren't a lot of people using this solution — it's not very popular in the marketplace. It's been around for 21 years, but not many people have heard of it. In the next release, it should support JSON, XML, and replication with third-party tools.
I've never had any issues with the solution, so I can't think of any improvements it would need. It would be interesting if they added functionality with redundancy, reputation, and variability.
I think the performance and features of the program can be improved. The scalability of the performance when using more than one process is not so good. I would also like more or better security.
Embedded Database Software is a specialized category of database management systems designed for integration within other applications. Unlike traditional database systems, which operate as standalone servers or services that applications connect to over a network, embedded databases run as part of the application itself.
We would like to improve the management of very large databases. We have databases up to three or four terabytes, and it's not so easy to manage such large databases.
Firebird SQL's performance has slowed since Firebird SQL 3 or 3.5 versions, where they developed over-the-wire encryption. I wouldn't recommend the solution to others for performance. The solution should add some monitoring features for the database. Firebird SQL should add the just-in-time dumps and journaling feature if it doesn't already have them.
The main feature I expect is to be able to work with different databases at the same time because that's a wishlist item for me. Part of the wishlist.
It is not easy to integrate the tool with Visual Studio.
Database sharing is a capability that Firebird SQL lacks. With database sharing, we can split the database into different machines. Database sharing is a functionality I would like to see in the solution, especially when implementing it at very large sites.
It would be nice to have a graphical user interface to handle the product. A lot of databases have it. I don't think Firebird has it. I use the ISQL directly. It's fine for me. However, it takes a while when you're creating databases and stuff. It would be helpful.
The security of the users could improve in Firebird SQL.
Technical support and performance could be better. We have some problems with this solution, but we don't know if the problem is with the database or the configuration. For example, sometimes, the users can't access the database.
This solution isn't very user-friendly, or intuitive, which could be improved when it is developed.
The solution could improve by providing partitioning and encryption. It is not at the higher level of database solution but it could be with some upgrades.
There aren't a lot of people using this solution — it's not very popular in the marketplace. It's been around for 21 years, but not many people have heard of it. In the next release, it should support JSON, XML, and replication with third-party tools.
It would be good to have more automation and integration with the tools from other vendors.
I've never had any issues with the solution, so I can't think of any improvements it would need. It would be interesting if they added functionality with redundancy, reputation, and variability.
I think the performance and features of the program can be improved. The scalability of the performance when using more than one process is not so good. I would also like more or better security.