The schema script '%1' could not be propagated to the subscriber due to an error in creating index. A possible cause of this error is one or more join filters has the join_unique_key property set to 1 when the join may not be unique.
The schema of the custom DataSet object implemented in the business logic handler does not match the schema of the source ...
The schema option to script out the FILESTREAM attribute on varbinary(max) columns has been enabled for article '%1!s!'. ...
The schema options available for a procedure, function, synonym, or aggregate schema article are: 0x00000001, 0x00000020, ...
The schema options available for a view schema article are: 0x00000001, 0x00000010, 0x00000020, 0x00000040, 0x00000100, 0x00001000, ...
The schema script '%1' could not be propagated to the subscriber due to an error in creating index. A possible cause of this ...
The schema {0} does not have any corresponding user or role. Schema objects are not supported in the target database version, ...
The score override argument, if present in one of the subqueries, must be present in all subqueries and must be the same ...
The script component is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script ...
The script exceeds the Transact-SQL IntelliSense maximum script size setting. You can change the setting on the Text Editor/Transact-SQL/IntelliSense ...