SQL Server and SSMS compatibility for CA Harvest SCM
search cancel

SQL Server and SSMS compatibility for CA Harvest SCM

book

Article ID: 442935

calendar_today

Updated On:

Products

CA Harvest Software Change Manager CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

This article clarifies support for Microsoft SQL Server versions and the necessity of SQL Server Management Studio (SSMS) when using CA Harvest Software Change Manager (SCM). Customers often ask if SSMS is required for the Harvest agent, server, or client to function, or if it is only needed for initial setup and maintenance.

Environment

  • Product: CA Harvest Software Change Manager (SCM)
  • Versions: 13.x, 14.x
  • Database: Microsoft SQL Server 2016, 2017, 2019, 2022
  • Platform: Windows

Resolution

CA Harvest SCM v14.x is certified for use with SQL Server 2016 through 2022

Is SQL Server Management Studio (SSMS) Required?

  • Runtime/Daily Operations: No. SSMS is not required for the Harvest Broker (server), Agent, or Client to perform daily software change management tasks.
  • Maintenance and Configuration: Yes. SSMS and the Microsoft Command Line Utilities for SQL Server are required on the Harvest Server machine to enable connectivity for the HDBSetup utility. This is necessary when the Harvest Database is hosted on a remote SQL Server instance.

If software currency requirements prohibit the presence of SSMS on production nodes, perform maintenance tasks from a dedicated management station or install SSMS temporarily during maintenance windows.

Maintenance Steps (Using HDBSetup): If the SQL Server version is updated, run the HDBSetup utility to ensure the ODBC connection remains valid:

  1. Ensure all Harvest-related processes (Bkrd.exe, hserver.exe) are stopped.
  2. Open a command prompt and navigate to the %CA_SCM_HOME% folder.
  3. Execute hdbsetup.exe.
  4. Select s for SQL Server.
  5. Select co from the main menu to configure the ODBC DSN.
  6. Follow prompts to verify the server name and authentication (SQL Server Authentication is recommended).
  7. Note: Use the SQL Server 2017 ODBC driver for connectivity, as issues have been reported with newer driver versions in some environments.
  8. Test the connection. Once "Connection test succeeded" appears, the upgrade is verified.

Additional Information

See also:

Upgrading Schema For a SQL Server Database with HDBSetup

SQL Server database migration to new server

Powered by Wolken Software