Skip to content

Conversation

alo-is
Copy link

@alo-is alo-is commented Apr 12, 2020

Description

Added support for character_set_name (also known as collation) in Microsoft SQL Server on RDS. This feature is optional, but supported in MSSQL on RDS.

Motivation and Context

Without this attribute, newly created MSSQL databases on RDS will be set to SQL_Latin1_General_CP1_CI_AS, which is the default value, but is incorrect in some cases when specific charsets are used, or with some software (we've got the issue with Sage Accounting solution).
The full AWS documentation regarding this attribute is available here : https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.SQLServer.CommonDBATasks.Collation.html

Breaking Changes

No impact on current version, if is attribute is left empty, then default value will apply as before (set by AWS, not this module).

How Has This Been Tested?

This change has been tested by deploying MSSQL 2017 Servers on RDS (express + web version). With & without the attribute, the changes are working as expected, changing the database default collation to the wanted one.

@alo-is alo-is changed the title Add support for character_set_name with MSSQL Server feat: Add support for character_set_name with MSSQL Server Apr 12, 2020
Copy link
Member

@antonbabenko antonbabenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

Few comments:

  1. Please add support to the same character_set_name into the root module.
  2. Update code in examples/complete-mssql example with this feature.

PS: If your PR is working as you say, could you also open an issue in https://github.com/terraform-providers/terraform-provider-aws and/or update documentation for this argument there.

Thanks!

@bryantbiggs
Copy link
Member

closed with #281

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants