Skip to content

tSQLt doesn't support contained databases #41

Description

@unclefr3d0

tSQLt doesn't support contained/partially contained databases. A number of collation issues (due to the changed in system catalogs - the sys* tables) means that tSQLt cannot be installed if the database collation is not Latin1_General_100_CI_AS_KS_WS_SC.

Msg 468, Level 16, State 9, Procedure Private_GetCursorForRunNew, Line 10 Cannot resolve the collation conflict between "Latin1_General_100_CI_AS_KS_WS_SC" and "Latin1_General_CI_AS" in the equal to operation. Msg 451, Level 16, State 1, Procedure Private_ScriptIndex, Line 32 Cannot resolve collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in add operator occurring in SELECT statement column 6. Msg 451, Level 16, State 1, Procedure Private_GetForeignKeyDefinition, Line 17 Cannot resolve collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in add operator occurring in SELECT statement column 1. Msg 451, Level 16, State 1, Procedure Private_GetForeignKeyDefinition, Line 17 Cannot resolve collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in add operator occurring in SELECT statement column 2. Msg 451, Level 16, State 1, Procedure Private_GetDataTypeOrComputedColumnDefinition, Line 4 Cannot resolve collation conflict between "Latin1_General_100_CI_AS_KS_WS_SC" and "Latin1_General_CI_AS" in CASE operator occurring in SELECT statement column 2. Msg 208, Level 16, State 1, Procedure Private_GetUniqueConstraintDefinition, Line 47 Invalid object name 'tSQLt.Private_GetDataTypeOrComputedColumnDefinition'.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions