Repository Connection

• Used throughout the Grooper UI, logs, and reports to identify the repository.
• Typically set during repository creation.
• Changing the name does not affect the repository's unique identity or database location.

The 'Server Name' property specifies the network address or name of the SQL Server instance. For default instances, use the server name or IP address. For named instances, use the format ServerName\InstanceName.

• This value is required for establishing a connection.
• For cloud or managed SQL, use the fully qualified domain name as provided by your service provider.

Example:
SQLSERVER01SQLSERVER01\SQLEXPRESSmyserver.database.windows.net

For more details, see the Microsoft documentation on Logging In to SQL Server.

The 'Database Name' property specifies the name of the database within the SQL Server instance that Grooper should connect to. This value is required for most operations, and must match the name of an existing database on the server.

• Use the dropdown in the property grid to select from available databases on the configured server.
• Changing the database name may require updating permissions or restarting services that depend on the connection.

Example:
GrooperRepository

The 'Connection Timeout' property controls how long Grooper will wait when attempting to establish a connection to the database server. If the connection cannot be made within the specified time, the attempt is aborted and an error is generated.

• Increase this value if connecting to remote or slow servers.
• Decrease it to fail fast in environments where quick feedback is preferred.

Example:
Set to 30 to allow up to 30 seconds for the connection to succeed.

• Assigned when the repository is created and never changes.
• Used internally to distinguish between different repositories, even if they have the same name.
• Essential for scripting, automation, and integration scenarios.

Can be one of the following values:

Indicates the health and compatibility of the repository database, such as whether it is online, needs an upgrade, or is a newer version.

• Used to determine if the repository is ready for use or requires maintenance.
• Automatically refreshed when accessed.

• Indicates the schema version of the connected repository database.
• Used to verify compatibility with the current Grooper application version.
• Automatically refreshed when the status is checked.
• Blank if the version cannot be determined.

The 'Connection String' property displays the full connection string used to connect to the database, with sensitive information such as passwords masked or removed for security. This allows you to verify the configuration without exposing credentials.

• Use this property to confirm that all required parameters are present and correct.
• The actual connection string used at runtime may include additional provider-specific options, depending on the derived class.

Example:
Server=myserver;Database=mydb;User Id=dbuser;Password=*****;Timeout=30;

The 'User Name' property specifies the account used to authenticate with the database server. If both 'User Name' and 'Password' are left blank, Grooper will use Windows Authentication (integrated security), which is recommended in environments where Active Directory is available and security policies require it.

• Enter a user name for SQL authentication or other explicit login scenarios.
• Leave blank to use the credentials of the Windows user running the Grooper service or application.

Example:
dbuser

The 'Password' property is used in conjunction with 'User Name' for explicit authentication to the database server. The password is stored in encrypted form and is never displayed in plain text in the UI.

• Leave blank to use Windows Authentication.
• Enter a password only when required by the database server and security policy.

Security Note:
The password is encrypted for storage, but always follow best practices for credential management.