The Safe rename refactor ignores table columns in JOIN clauses and generates incorrect refactoring script

Applies to
ApexSQL Refactor

Summary
This article explains the issue when renaming a table column used in the JOIN clause and executing the created refactoring script.

Symptoms
A table column is referenced in the JOIN clause of another object (stored procedure, view, user-defined function): 

CREATE PROCEDURE dbo.uspArticle
AS
BEGIN

SELECT
 a1.ArticleID 
,a1.ArticleMonthlyContent
,a2.ArticleWeeklyContent
FROM dbo.ArticleMonth a1
INNER JOIN dbo.ArticleWeek a2 
ON a1.ArticleID=a2.ArticleID
END

If a table column is refactored using the Smart rename feature a column will not be renamed in the JOIN clause:

Smart rename column dialog - column will not be renamed in the JOIN clause

When the user tries to execute the generated script by clicking the Rename now button, the execution will fail:

Script execution results dialog - execution failed

Background
Due to a bug in the ApexSQL Refactor, refactored table columns were ignored in join clauses and the generated script execution would fail.

Affected versions:
ApexSQL Refactor 2013.04.0050 and older

Resolution
This issue has been solved in the latest ApexSQL Refactor that can be downloaded from here

Related posts:

  1. The ‘Sqlcmd: Error: Syntax error at line XYZ near command ‘X’ in file ‘file_name.sql’.’ error is encountered when running SQL script via sqlcmd utility
  2. ApexSQL Recover doesn’t recover all lost data
  3. An object containing special characters in the schema name is shown as non-existing on a database side in the Action center tab after the initial commit is finished
  4. Objects are shown in the Action center tab as non-existing on both sides and history for those objects is not accessible
  5. The synchronization script is generated with errors when synchronizing a specific database with an empty database as a destination