# How can I test a database change before using it in production?

Canonical URL: https://help.iagenify.com/faqs/databases/how-can-i-test-a-database-change-before-using-it-in-production

[← Back to Databases FAQs](https://help.iagenify.com/faqs/databases)

HELP CENTER · FAQ Databases 2 min read
# How can I test a database change before using it in production?
Database changes can affect existing records as well as new ones. A separate test environment lets you check the query and its assumptions before applying the same idea to production data.
IaGenify
Databases

## Make the test environment unmistakable
Use a development database or a deliberately small test dataset with representative examples. Confirm the connection name, database, and environment before running a query that writes, updates, or deletes records. Similar connection labels can make it easy to mistake a production target for a test target, so verify the destination explicitly.
Start with a read-only query or a limited sample to understand which records match. Check edge cases such as missing values, duplicate identifiers, and older records that may not follow the newest format. This helps expose assumptions before a broader change can affect more data.
## Review the effect before widening the change
When the test behaves as expected, compare the proposed change with the current schema and application behavior. Confirm that dependent workflows or agents can still read the resulting fields and that any new requirement is reflected where records are created. A successful query alone does not prove the whole application remains compatible.
Keep a record of the tested query, target environment, and expected outcome. Before applying it to production, verify the selected connection again and consider how you would recover if the result is wrong. Make the production change in a controlled step and inspect the affected records afterward rather than assuming the test guarantees success. [← Back to Databases FAQs](https://help.iagenify.com/faqs/databases)