XSD Identities for GradebookEntry's LearningObjective and LearningStandard too big for SQL Server

GradebookEntry has collections of LearningObjectives and LearningStandards. These collections map to tables in the ODS. Unfortunately, the combined size of the identity elements for these collections exceed the maximum size allowable for a primary key in the corresponding ODS tables. This means inserts/updates of GradebookEntry LearningStandards and/or LearningObjectives may fail even though the data meets Data Standard length requirements.

This was noticed during MetaEd 0.7 testing, but is not a MetaEd related issue. This is the existing behavior when the 2.0 Final ODS is built. Excerpt of the 2.0 Final 0004-Tables.SQL log:

<<< CREATED TABLE edfi.GradebookEntry >>>
Warning! The maximum key length is 900 bytes. The index 'PK_GradebookEntryLearningObjective' has maximum length of 975 bytes. For some combination of large values, the insert/update operation will fail.
<<< CREATED TABLE edfi.GradebookEntryLearningObjective >>>
Warning! The maximum key length is 900 bytes. The index 'PK_GradebookEntryLearningStandard' has maximum length of 967 bytes. For some combination of large values, the insert/update operation will fail.
<<< CREATED TABLE edfi.GradebookEntryLearningStandard >>>

Placing this issue in the DATASTD Jira project to start as there are no easy ODS workarounds.