Skip to content

AgentPrismSqlServerOptions

Namespace AgentPrism · Assembly AgentPrism.SqlServer.dll

Settings for AgentPrism’s SQL Server persistence layer.

public sealed class AgentPrismSqlServerOptions

objectAgentPrismSqlServerOptions

object.GetType(), object.ToString(), object.Equals(object?), object.Equals(object?, object?), object.ReferenceEquals(object?, object?), object.GetHashCode()

Validation is done by hand in AgentPrismSqlServerOptionsValidator; DataAnnotations is not used.

public AgentPrismSqlServerOptions()

The full path of the configuration section settings are read from.

public const string SectionName = "AgentPrism:SqlServer"

string

Whether pending migrations are applied automatically at application startup.

public bool AutoApplyMigrations { get; set; }

bool

Can be set to false in production and MigrationRunner run as a separate deployment step, so a long-running migration does not block application startup.

The upper time limit for a single SQL command (seconds). 0 means unlimited.

public int CommandTimeoutSeconds { get; set; }

int

The SQL Server connection string.

public string? ConnectionString { get; set; }

string?

This value is a secret and is never written to a file. Use dotnet user-secrets, an environment variable, or a secret manager.

The schema AgentPrism’s tables are created in. The consumer’s dbo schema is never touched, under any circumstances.

public string SchemaName { get; set; }

string

Even though SQL Server allows a wider set of identifiers, AgentPrism enforces the same strict rule: starts with a lowercase letter or underscore, contains lowercase letters, digits, and underscores, at most 63 characters. This way the same schema name carries over between PostgreSQL and SQL Server without changes.