SSDT (I suspect) creates a table called __RefactorLog in any database you point it towards.
SSDT（我怀疑）在你指向它的任何数据库中创建一个名为__RefactorLog的表。
If I've hit a release is there any harm in deleting this table as I don't see any benefit in including it in schema creation scripts at the time of deployment?
如果我发布了一个版本是否有任何损害删除此表，因为我没有看到在部署时将其包含在架构创建脚本中的任何好处？
I can't see any downside to it myself, but I'd like to pose the question to the knowledgeable people here to see if there's something I'm missing...
我自己也看不出任何不利因素，但是我想向这里知识渊博的人提出问题，看看是否有我遗漏的东西......
1 个解决方案
#1
9
It is created by SSDT when you use a refactor in SSDT (like Refactor -> Rename) if you do a deployment and just clear out the table it will retry to do any old refactorings which could just fail or cause a disaster!
它是由SSDT在SSDT中使用重构器（如Refactor - > Rename）创建的，如果您进行部署并清除表格，它将重试进行任何可能失败或导致灾难的旧重构！
If you clear the table make sure you also remove the entries from the refactorlog.xml in your project - the file is pretty obvious.
如果清除表，请确保还从项目中的refactorlog.xml中删除条目 - 该文件非常明显。
Make sure you don't try to deploy an old dacpac (I guess this is unlikely anyway)
确保你没有尝试部署一个旧的dacpac（我想这不太可能）
Ed
埃德
#1
9
It is created by SSDT when you use a refactor in SSDT (like Refactor -> Rename) if you do a deployment and just clear out the table it will retry to do any old refactorings which could just fail or cause a disaster!
它是由SSDT在SSDT中使用重构器（如Refactor - > Rename）创建的，如果您进行部署并清除表格，它将重试进行任何可能失败或导致灾难的旧重构！
If you clear the table make sure you also remove the entries from the refactorlog.xml in your project - the file is pretty obvious.
如果清除表，请确保还从项目中的refactorlog.xml中删除条目 - 该文件非常明显。
Make sure you don't try to deploy an old dacpac (I guess this is unlikely anyway)
确保你没有尝试部署一个旧的dacpac（我想这不太可能）
Ed
埃德