How to Set the Schema Name Dynamically in Spring JPA?

Last Updated : 23 Apr, 2026

In Spring Data JPA, dynamic schema configuration allows applications to switch database schemas at runtime without modifying entity classes. This is especially useful in multi-tenant systems and environment-based deployments where schema flexibility is required.

  • Enables dynamic switching between schemas using configuration or environment variables
  • Achieved through a custom Hibernate naming strategy or JPA properties
  • Improves flexibility and maintainability in scalable applications

Step-by-Step Implementation

Follow these steps to configure and implement dynamic schema resolution in Spring JPA using a custom strategy or application properties.

Step 1: Create a Custom Naming Strategy Class

  • Extend an existing naming strategy like CamelCaseToUnderscoresNamingStrategy.
  • Override toPhysicalSchemaName() to define dynamic schema logic.
  • Fetch schema name from environment variable or config.
Java 
package com.geeksforgeeks;

import org.hibernate.boot.model.naming.CamelCaseToUnderscoresNamingStrategy;
import org.hibernate.boot.model.naming.Identifier;
import org.hibernate.engine.jdbc.env.spi.JdbcEnvironment;

public class DynamicSchemaNamingStrategy extends CamelCaseToUnderscoresNamingStrategy {

    @Override
    public Identifier toPhysicalSchemaName(Identifier name, JdbcEnvironment context) {

        String schemaName = System.getenv("SCHEMA_NAME");

        if (schemaName == null || schemaName.isEmpty()) {
            throw new IllegalArgumentException("Environment variable 'SCHEMA_NAME' is not set");
        }

        return Identifier.toIdentifier(schemaName);
    }
}

Step 2: Implement Logic for Schema Resolution

  • Use System.getenv("SCHEMA_NAME") or application properties.
  • Add validation to handle missing values.
  • Return schema dynamically based on condition.

Step 3: Configure in application.properties

  • Replace with your package name.
  • This tells Hibernate to use your custom strategy.

# Use custom naming strategy
spring.jpa.hibernate.naming.physical-strategy=com.geeksforgeeks.DynamicSchemaNamingStrategy

Step 4: Use Dynamic Schema in Entity Class

Java 
package com.geeksforgeeks.entity;

import jakarta.persistence.*;

@Entity
@Table(name = "user")   
public class User {

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    private String name;

    // Getters and Setters
    public Long getId() {
        return id;
    }

    public String getName() {
        return name;
    }

    public void setId(Long id) {
        this.id = id;
    }

    public void setName(String name) {
        this.name = name;
    }
}

Step 5: Set Environment Variable

Define schema name externally:

Linux / Mac: export SCHEMA_NAME=my_schema

Windows (CMD): set SCHEMA_NAME=my_schema

Step 6: Run and Verify

  • Start your Spring Boot application.
  • Check logs or database to confirm tables are created in the correct schema.

Additional Considerations

  • Error handling: Make sure to handle any errors that might occur when trying to determine the schema name, such as if an environment variable is not set.
  • Performance: Dynamically setting the schema name can have a slight performance impact, as the schema name needs to be resolved for each entity operation. If performance is critical, you may want to consider using a different approach, such as using a separate data source for each schema.
  • Security: If you are storing sensitive data in different schemas, you need to make sure that only authorized users have access to the data. This may require implementing additional security measures, such as using role-based access control (RBAC).
Comment

Explore