Berkeley DB Feature Survey

Berkeley DB Future Features

The Berkeley DB team wants to hear from you!

What follows is a list of potential features that we're considering for future Berkeley DB releases. We'd like your feedback on this list, comments about how you use Berkeley DB and suggestions for additional features that you would like to see in the future. Although we are very interested in hearing your opinion, this survey does not constitute a commitment to implement any of the features listed below.

This survey is specifically for the Berkeley DB product. It is not intended to address features for Berkeley DB XML or Berkeley DB Java Edition. We will have future surveys for those products.

Thank you,

Oracle Berkeley DB Product Management

1. The BDB team is considering the following features. For each feature, please indicate the relative importance of that feature for you.

	Absolutely Do This	Very Interesting	OK	Not Very Interesting	Don't Bother
Integration: Oracle Enterprise Manager integration	*The BDB team is considering the following features. For each feature, please indicate the relative importance of that feature for you. Integration: Oracle Enterprise Manager integration Absolutely Do This	Integration: Oracle Enterprise Manager integration Very Interesting	Integration: Oracle Enterprise Manager integration OK	Integration: Oracle Enterprise Manager integration Not Very Interesting	Integration: Oracle Enterprise Manager integration Don't Bother
Integration: Integration with a generic report writer (JDBC, ODBC or ADO.NET). Please specify which report writer(s) would be of particular interested to you in the space provided for Question 2.	Integration: Integration with a generic report writer (JDBC, ODBC or ADO.NET). Please specify which report writer(s) would be of particular interested to you in the space provided for Question 2. Absolutely Do This	Integration: Integration with a generic report writer (JDBC, ODBC or ADO.NET). Please specify which report writer(s) would be of particular interested to you in the space provided for Question 2. Very Interesting	Integration: Integration with a generic report writer (JDBC, ODBC or ADO.NET). Please specify which report writer(s) would be of particular interested to you in the space provided for Question 2. OK	Integration: Integration with a generic report writer (JDBC, ODBC or ADO.NET). Please specify which report writer(s) would be of particular interested to you in the space provided for Question 2. Not Very Interesting	Integration: Integration with a generic report writer (JDBC, ODBC or ADO.NET). Please specify which report writer(s) would be of particular interested to you in the space provided for Question 2. Don't Bother
Locking: Distributed Lock Manager. Basically this would allow BDB to be stored on a shared disk resource and accessed from multiple systems. Since distributed lock coordination requires additional coordination and overhead, if enabled this feature will impact transaction throughput.	Locking: Distributed Lock Manager. Basically this would allow BDB to be stored on a shared disk resource and accessed from multiple systems. Since distributed lock coordination requires additional coordination and overhead, if enabled this feature will impact transaction throughput. Absolutely Do This	Locking: Distributed Lock Manager. Basically this would allow BDB to be stored on a shared disk resource and accessed from multiple systems. Since distributed lock coordination requires additional coordination and overhead, if enabled this feature will impact transaction throughput. Very Interesting	Locking: Distributed Lock Manager. Basically this would allow BDB to be stored on a shared disk resource and accessed from multiple systems. Since distributed lock coordination requires additional coordination and overhead, if enabled this feature will impact transaction throughput. OK	Locking: Distributed Lock Manager. Basically this would allow BDB to be stored on a shared disk resource and accessed from multiple systems. Since distributed lock coordination requires additional coordination and overhead, if enabled this feature will impact transaction throughput. Not Very Interesting	Locking: Distributed Lock Manager. Basically this would allow BDB to be stored on a shared disk resource and accessed from multiple systems. Since distributed lock coordination requires additional coordination and overhead, if enabled this feature will impact transaction throughput. Don't Bother
Access Methods: Support database compaction for the HEAP and/or HASH access methods. Please provide details in the space provided for Question 2 about which access method is most important for you.	Access Methods: Support database compaction for the HEAP and/or HASH access methods. Please provide details in the space provided for Question 2 about which access method is most important for you. Absolutely Do This	Access Methods: Support database compaction for the HEAP and/or HASH access methods. Please provide details in the space provided for Question 2 about which access method is most important for you. Very Interesting	Access Methods: Support database compaction for the HEAP and/or HASH access methods. Please provide details in the space provided for Question 2 about which access method is most important for you. OK	Access Methods: Support database compaction for the HEAP and/or HASH access methods. Please provide details in the space provided for Question 2 about which access method is most important for you. Not Very Interesting	Access Methods: Support database compaction for the HEAP and/or HASH access methods. Please provide details in the space provided for Question 2 about which access method is most important for you. Don't Bother
Access Methods: Add support for API based (non-SQL) triggers on data operations.	Access Methods: Add support for API based (non-SQL) triggers on data operations. Absolutely Do This	Access Methods: Add support for API based (non-SQL) triggers on data operations. Very Interesting	Access Methods: Add support for API based (non-SQL) triggers on data operations. OK	Access Methods: Add support for API based (non-SQL) triggers on data operations. Not Very Interesting	Access Methods: Add support for API based (non-SQL) triggers on data operations. Don't Bother
Data Management: Add support enabling access of non-SQL data via the SQL API and/or access of SQL data via the key-value API. Please provide details in the space provided for Question 2 about which form of access is most important to you.	Data Management: Add support enabling access of non-SQL data via the SQL API and/or access of SQL data via the key-value API. Please provide details in the space provided for Question 2 about which form of access is most important to you. Absolutely Do This	Data Management: Add support enabling access of non-SQL data via the SQL API and/or access of SQL data via the key-value API. Please provide details in the space provided for Question 2 about which form of access is most important to you. Very Interesting	Data Management: Add support enabling access of non-SQL data via the SQL API and/or access of SQL data via the key-value API. Please provide details in the space provided for Question 2 about which form of access is most important to you. OK	Data Management: Add support enabling access of non-SQL data via the SQL API and/or access of SQL data via the key-value API. Please provide details in the space provided for Question 2 about which form of access is most important to you. Not Very Interesting	Data Management: Add support enabling access of non-SQL data via the SQL API and/or access of SQL data via the key-value API. Please provide details in the space provided for Question 2 about which form of access is most important to you. Don't Bother
Data Management: Add support for automatic data aging (deletion) based on some criteria (time-to-live and/or disk space, for example).	Data Management: Add support for automatic data aging (deletion) based on some criteria (time-to-live and/or disk space, for example). Absolutely Do This	Data Management: Add support for automatic data aging (deletion) based on some criteria (time-to-live and/or disk space, for example). Very Interesting	Data Management: Add support for automatic data aging (deletion) based on some criteria (time-to-live and/or disk space, for example). OK	Data Management: Add support for automatic data aging (deletion) based on some criteria (time-to-live and/or disk space, for example). Not Very Interesting	Data Management: Add support for automatic data aging (deletion) based on some criteria (time-to-live and/or disk space, for example). Don't Bother
Data Management: Add a schema description layer for non-SQL APIs (key-value, Java collections, Java DPL).	Data Management: Add a schema description layer for non-SQL APIs (key-value, Java collections, Java DPL). Absolutely Do This	Data Management: Add a schema description layer for non-SQL APIs (key-value, Java collections, Java DPL). Very Interesting	Data Management: Add a schema description layer for non-SQL APIs (key-value, Java collections, Java DPL). OK	Data Management: Add a schema description layer for non-SQL APIs (key-value, Java collections, Java DPL). Not Very Interesting	Data Management: Add a schema description layer for non-SQL APIs (key-value, Java collections, Java DPL). Don't Bother
Indexing: Full Text Index search. Add support for full text indices, which may include support for stemming, stop words, regular expressions and wildcard searches.	Indexing: Full Text Index search. Add support for full text indices, which may include support for stemming, stop words, regular expressions and wildcard searches. Absolutely Do This	Indexing: Full Text Index search. Add support for full text indices, which may include support for stemming, stop words, regular expressions and wildcard searches. Very Interesting	Indexing: Full Text Index search. Add support for full text indices, which may include support for stemming, stop words, regular expressions and wildcard searches. OK	Indexing: Full Text Index search. Add support for full text indices, which may include support for stemming, stop words, regular expressions and wildcard searches. Not Very Interesting	Indexing: Full Text Index search. Add support for full text indices, which may include support for stemming, stop words, regular expressions and wildcard searches. Don't Bother
SQL API: Support for table disk location definition, allowing application to specify where to store data for a given table/database.	SQL API: Support for table disk location definition, allowing application to specify where to store data for a given table/database. Absolutely Do This	SQL API: Support for table disk location definition, allowing application to specify where to store data for a given table/database. Very Interesting	SQL API: Support for table disk location definition, allowing application to specify where to store data for a given table/database. OK	SQL API: Support for table disk location definition, allowing application to specify where to store data for a given table/database. Not Very Interesting	SQL API: Support for table disk location definition, allowing application to specify where to store data for a given table/database. Don't Bother
SQL API: Support for table partitioning, allowing the application to define partitioning scheme and partition location on disk.	SQL API: Support for table partitioning, allowing the application to define partitioning scheme and partition location on disk. Absolutely Do This	SQL API: Support for table partitioning, allowing the application to define partitioning scheme and partition location on disk. Very Interesting	SQL API: Support for table partitioning, allowing the application to define partitioning scheme and partition location on disk. OK	SQL API: Support for table partitioning, allowing the application to define partitioning scheme and partition location on disk. Not Very Interesting	SQL API: Support for table partitioning, allowing the application to define partitioning scheme and partition location on disk. Don't Bother
SQL API: Allow writes to BFILE extension. Extend the current BFile extension to allow writes as well as reads.	SQL API: Allow writes to BFILE extension. Extend the current BFile extension to allow writes as well as reads. Absolutely Do This	SQL API: Allow writes to BFILE extension. Extend the current BFile extension to allow writes as well as reads. Very Interesting	SQL API: Allow writes to BFILE extension. Extend the current BFile extension to allow writes as well as reads. OK	SQL API: Allow writes to BFILE extension. Extend the current BFile extension to allow writes as well as reads. Not Very Interesting	SQL API: Allow writes to BFILE extension. Extend the current BFile extension to allow writes as well as reads. Don't Bother
SQL API: Add ability to specify HEAP or HASH access methods in addition to the default B-Tree support.	SQL API: Add ability to specify HEAP or HASH access methods in addition to the default B-Tree support. Absolutely Do This	SQL API: Add ability to specify HEAP or HASH access methods in addition to the default B-Tree support. Very Interesting	SQL API: Add ability to specify HEAP or HASH access methods in addition to the default B-Tree support. OK	SQL API: Add ability to specify HEAP or HASH access methods in addition to the default B-Tree support. Not Very Interesting	SQL API: Add ability to specify HEAP or HASH access methods in addition to the default B-Tree support. Don't Bother
SQL API: Add support for multi-row bulk operations.	SQL API: Add support for multi-row bulk operations. Absolutely Do This	SQL API: Add support for multi-row bulk operations. Very Interesting	SQL API: Add support for multi-row bulk operations. OK	SQL API: Add support for multi-row bulk operations. Not Very Interesting	SQL API: Add support for multi-row bulk operations. Don't Bother
HA: Add support for multi-master replication.	HA: Add support for multi-master replication. Absolutely Do This	HA: Add support for multi-master replication. Very Interesting	HA: Add support for multi-master replication. OK	HA: Add support for multi-master replication. Not Very Interesting	HA: Add support for multi-master replication. Don't Bother
HA: Add support for write-anywhere replication via write forwarding.	HA: Add support for write-anywhere replication via write forwarding. Absolutely Do This	HA: Add support for write-anywhere replication via write forwarding. Very Interesting	HA: Add support for write-anywhere replication via write forwarding. OK	HA: Add support for write-anywhere replication via write forwarding. Not Very Interesting	HA: Add support for write-anywhere replication via write forwarding. Don't Bother
HA: Partial replication. Allow a replica to contain a subset of database tables. A partial replica would support read operations, but would not be able to become a master.	HA: Partial replication. Allow a replica to contain a subset of database tables. A partial replica would support read operations, but would not be able to become a master. Absolutely Do This	HA: Partial replication. Allow a replica to contain a subset of database tables. A partial replica would support read operations, but would not be able to become a master. Very Interesting	HA: Partial replication. Allow a replica to contain a subset of database tables. A partial replica would support read operations, but would not be able to become a master. OK	HA: Partial replication. Allow a replica to contain a subset of database tables. A partial replica would support read operations, but would not be able to become a master. Not Very Interesting	HA: Partial replication. Allow a replica to contain a subset of database tables. A partial replica would support read operations, but would not be able to become a master. Don't Bother
HA: Add notification triggers on the replica. Allow a replicated application to know when certain data changes occur due to replication.	HA: Add notification triggers on the replica. Allow a replicated application to know when certain data changes occur due to replication. Absolutely Do This	HA: Add notification triggers on the replica. Allow a replicated application to know when certain data changes occur due to replication. Very Interesting	HA: Add notification triggers on the replica. Allow a replicated application to know when certain data changes occur due to replication. OK	HA: Add notification triggers on the replica. Allow a replicated application to know when certain data changes occur due to replication. Not Very Interesting	HA: Add notification triggers on the replica. Allow a replicated application to know when certain data changes occur due to replication. Don't Bother
Security: Add an API to support user authentication. Today this is typically handled by the embedding application.	Security: Add an API to support user authentication. Today this is typically handled by the embedding application. Absolutely Do This	Security: Add an API to support user authentication. Today this is typically handled by the embedding application. Very Interesting	Security: Add an API to support user authentication. Today this is typically handled by the embedding application. OK	Security: Add an API to support user authentication. Today this is typically handled by the embedding application. Not Very Interesting	Security: Add an API to support user authentication. Today this is typically handled by the embedding application. Don't Bother
Security: Add an API to provide an audit log, with details beyond what is currently available from the BDB transaction log today.	Security: Add an API to provide an audit log, with details beyond what is currently available from the BDB transaction log today. Absolutely Do This	Security: Add an API to provide an audit log, with details beyond what is currently available from the BDB transaction log today. Very Interesting	Security: Add an API to provide an audit log, with details beyond what is currently available from the BDB transaction log today. OK	Security: Add an API to provide an audit log, with details beyond what is currently available from the BDB transaction log today. Not Very Interesting	Security: Add an API to provide an audit log, with details beyond what is currently available from the BDB transaction log today. Don't Bother
Security: Add an API to support adding user/operation/object permissions. Today this is typically handled by the embedding application.	Security: Add an API to support adding user/operation/object permissions. Today this is typically handled by the embedding application. Absolutely Do This	Security: Add an API to support adding user/operation/object permissions. Today this is typically handled by the embedding application. Very Interesting	Security: Add an API to support adding user/operation/object permissions. Today this is typically handled by the embedding application. OK	Security: Add an API to support adding user/operation/object permissions. Today this is typically handled by the embedding application. Not Very Interesting	Security: Add an API to support adding user/operation/object permissions. Today this is typically handled by the embedding application. Don't Bother
General performance and throughput enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2.	General performance and throughput enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Absolutely Do This	General performance and throughput enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Very Interesting	General performance and throughput enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. OK	General performance and throughput enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Not Very Interesting	General performance and throughput enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Don't Bother
General documentation and examples enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2.	General documentation and examples enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Absolutely Do This	General documentation and examples enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Very Interesting	General documentation and examples enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. OK	General documentation and examples enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Not Very Interesting	General documentation and examples enhancements. Please specify which areas are of particular interested to you in the space provided for Question 2. Don't Bother
Comparative benchmark enhancements. Take an existing comparative benchmark and spend time implementing and/or enhancing the Berkeley DB implementation for that benchmark. Please specify which benchmark(s) are of particular interested to you in the space provided for Question 2.	Comparative benchmark enhancements. Take an existing comparative benchmark and spend time implementing and/or enhancing the Berkeley DB implementation for that benchmark. Please specify which benchmark(s) are of particular interested to you in the space provided for Question 2. Absolutely Do This	Comparative benchmark enhancements. Take an existing comparative benchmark and spend time implementing and/or enhancing the Berkeley DB implementation for that benchmark. Please specify which benchmark(s) are of particular interested to you in the space provided for Question 2. Very Interesting	Comparative benchmark enhancements. Take an existing comparative benchmark and spend time implementing and/or enhancing the Berkeley DB implementation for that benchmark. Please specify which benchmark(s) are of particular interested to you in the space provided for Question 2. OK	Comparative benchmark enhancements. Take an existing comparative benchmark and spend time implementing and/or enhancing the Berkeley DB implementation for that benchmark. Please specify which benchmark(s) are of particular interested to you in the space provided for Question 2. Not Very Interesting	Comparative benchmark enhancements. Take an existing comparative benchmark and spend time implementing and/or enhancing the Berkeley DB implementation for that benchmark. Please specify which benchmark(s) are of particular interested to you in the space provided for Question 2. Don't Bother