Git Integration in Toad for SQL Server (4380559)

Users want to configure Git integration in Toad for SQL Server and need clarification on supported features, limitations, and usage with Azure DevOps repositories. 

Git functionality in Toad for SQL Server is limited to local repository management. Remote repository operations and advanced Git workflows are not supported within the application.

• Local Git Only: Toad connects to a local Git repository on the workstation. Remote sync operations (clone, pull, push, branch, merge) must be performed externally using Git Bash, Git GUI, or another client.

• Database Object Versioning (via Object Explorer): Supported objects include tables, views, stored procedures, functions, sequences, UDDTs, rules, defaults, and SQL scripts.

• File Versioning (via File Editor): Files such as .sql, .tef, .ter, and .tas can be versioned using the version control wizard. This is primarily designed for SVN; Git support may work indirectly.

• Rename Handling: Renamed objects lose their version history. Toad treats them as new objects.

• Unsupported Objects: CLR objects are not supported.  CLR objects in SQL Server are database objects implemented using the .NET Common Language Runtime (CLR) instead of traditional T-SQL. Essentially, SQL Server allows you to write code in .NET languages (like C# or VB.NET) and use it inside the database as if it were a native SQL object. 

• Azure DevOps: A Git repository hosted on Azure DevOps can be cloned locally and linked with Toad. Toad only recognizes the local copy. Synchronization with the remote repository must be handled outside of Toad.