A common question is whether database performance development can qualify as research and development for the federal R&D tax credit under Section 41. The short answer is that database performance development may constitute qualified research when it involves a technical uncertainty and a process of experimentation. Routine database administration and tuning generally is not qualified research, and internal-use software rules may apply. This page explains the framework in general terms. It is educational and is not individualized advice. For the foundational framework, see our page on qualified research.
When Database Performance Development May Warrant Review
Database performance development may warrant review when the work involves a genuine technical uncertainty and a process of experimentation. Under the four-part test, the work must be for a permitted purpose, be technological in nature, be intended to eliminate uncertainty, and be conducted through a process of experimentation.
Common scenarios that may warrant review include:
- New data-scale uncertainty — evaluating alternative approaches to resolve uncertainty about whether a database can handle a new data scale.
- Query performance — testing alternative approaches to resolve uncertainty about whether queries can achieve the required performance at a new scale.
- Data model development — evaluating alternative data models to resolve uncertainty about which can achieve the required performance.
- New technology — testing alternative database technologies to resolve uncertainty about whether a new technology can achieve the required performance.
Routine Administration vs. Performance Development
A central distinction is between routine database administration and performance development:
- Routine administration — performing standard database tuning, indexing, and maintenance using established methods. There is no technical uncertainty. This is administration, not research.
- Performance development — developing new database approaches where there is a technical uncertainty about whether the database can achieve the required performance, and evaluating alternatives to resolve that uncertainty. This may warrant review.
Hypothetical Example
Consider a company that is developing a new database approach to handle a new class of high-volume queries and is uncertain whether any available approach can achieve the required query performance at the target scale. The company evaluates alternative database technologies and data models, tests each, and systematically varies the approach to resolve the uncertainty. This systematic evaluation of alternatives may warrant review as qualified research.
By contrast, if the same company performs standard index tuning on an existing database, that is routine administration, not research.
This example is illustrative only and does not state that the activity definitely qualifies.
Documentation That May Help
Records that can help support database performance development claims include design records identifying the uncertainty and alternative approaches, performance test results, and records of how results informed database design decisions. For more, see our page on R&D tax credit documentation.
Key Takeaway
Database performance development may constitute qualified research when it involves a technical uncertainty and a process of experimentation. Routine database administration and tuning generally is not qualified research, and internal-use software rules may apply. Because the distinction is fact-specific, professional review is appropriate before claiming the credit.