所以事实证明,重构日志中有一些非常古老的东西。我要求发布步骤生成脚本而不是立即发布并搜索UnexpectedColumnName
:
GO
PRINT N'The following operation was generated from a refactoring log file 69ad6ffa-f53e-4302-a9af-a6f6907e4eec, 5879552a-9f2d-439c-82c8-352bbee08bb2';
PRINT N'Rename [dbo].[MyTableName].[ArbitraryRealColumnName] to UnexpectedColumnName';
GO
EXECUTE sp_rename @objname = N'[dbo].[MyTableName].[ArbitraryRealColumnName]', @newname = N'UnexpectedColumnName', @objtype = N'COLUMN';
然后我查看了重构日志,发现它与 GUID 匹配:
<Operation Name="Rename Refactor" Key="5879552a-9f2d-439c-82c8-352bbee08bb2" ChangeDateTime="02/13/2020 20:07:08">
<Property Name="ElementName" Value="[dbo].[MyTableName].[NotSureWhatThisIs]" />
<Property Name="ElementType" Value="SqlSimpleColumn" />
<Property Name="ParentElementName" Value="[dbo].[MyTableName]" />
<Property Name="ParentElementType" Value="SqlTable" />
<Property Name="NewName" Value="UnexpectedColumnName" />
</Operation>
因为我们不使用那些重构日志功能,所以我只是删除了整个重构日志,一切正常。我想你也可以删除错误的重命名。