1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
I perceive it as the SCT bug unable to proceed in case the collation of a database is different from the server instance.
This is because I see this error in the log:
Error executing 'get-server-config' query: com.microsoft.sqlserver.jdbc.SQLServerException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation
So my server was on the SQL_Latin1_General_CI_AS, but the database on the Latin1_General_CI_AS collation which is a valid setup in my view. Alas, the tool can't support this simple case.
Remedied by
ALTER DATABASE <name>
COLLATE SQL_Latin1_General_CP1_CI_AS;
回答済み 4年前
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 2年前