<_locDefinition xmlns="urn:locstudio"> <_locDefault _loc="locNone" /> <_locTag _loc="locData">DMF:Name <_locTag _loc="locData">DMF:Description <_locTag _loc="locData">DMF:Condition <_locTag _loc="locData">DMF:ObjectSet <_locTag _loc="locData">DMF:RootCondition <_locTag _loc="locData">DMF:PolicyCategory <_locTag _loc="locData">DMF:HelpText urn:uuid:96fe1236-abf6-4a57-b54d-e9baab394fd1 http://documentcollection/ /system/schema/DMF /PolicyStore/Policy/Database Collation /PolicyStore /PolicyStore/Condition/Collation Matches master or model /PolicyStore/ObjectSet/Database Collation__ObjectSet /PolicyStore/PolicyCategory/Microsoft Best Practices_b Performance Database Collation Looks for user-defined databases that have a collation different from the master or model databases. It is recommended that you not use this configuration because collation conflicts can occur that might prevent code from executing. For example, when a stored procedure joins one table to a temporary table, SQL Server might end the batch and return a collation conflict error if the collations of the user-defined database and the model database are different. This happens because temporary tables are created in tempdb, which obtains its collation based on that of the model database. If you experience collation conflict errors, consider one of the following solutions:<?char 13?> * Export the data from the user database and import it into new tables that have the same collation as the master and model databases.<?char 13?> * Rebuild the system databases to use a collation that matches the user database collation.<?char 13?> * Modify any stored procedures that join user tables to tables in tempdb to create the tables in tempdb by using the collation of the user database. To do this, add the COLLATE database_default clause to the column definitions of the temporary table. For example: CREATE TABLE #temp1 ( c1 int, c2 varchar(30) COLLATE database_default ) Collation Matches master or model Database Collation_ObjectSet Microsoft Best Practices: Performance false None http://go.microsoft.com/fwlink/?LinkId=116336 0001-01-01T00:00:00 0001-01-01T00:00:00 /PolicyStore/ObjectSet/Database Collation__ObjectSet /PolicyStore/ObjectSet/Database Collation__ObjectSet/TargetSet/Server_/Database /PolicyStore Database Collation_ObjectSet IDatabasePerformanceFacet /PolicyStore/Condition/Collation Matches master or model /PolicyStore <Operator><?char 13?> <TypeClass>Bool</TypeClass><?char 13?> <OpType>EQ</OpType><?char 13?> <Count>2</Count><?char 13?> <Attribute><?char 13?> <TypeClass>Bool</TypeClass><?char 13?> <Name>CollationMatchesModelOrMaster</Name><?char 13?> </Attribute><?char 13?> <Function><?char 13?> <TypeClass>Bool</TypeClass><?char 13?> <FunctionType>True</FunctionType><?char 13?> <ReturnType>Bool</ReturnType><?char 13?> <Count>0</Count><?char 13?> </Function><?char 13?> </Operator> Collation Matches master or model Confirms that the collation of the database matches the master or model databases. IDatabasePerformanceFacet /PolicyStore/PolicyCategory/Microsoft Best Practices_b Performance /PolicyStore Microsoft Best Practices: Performance /PolicyStore/ObjectSet/Database Collation__ObjectSet/TargetSet/Server_/Database /PolicyStore/ObjectSet/Database Collation__ObjectSet/TargetSet/Server_/Database/TargetSetLevel/Server_/Database /PolicyStore/ObjectSet/Database Collation__ObjectSet Server/Database true /PolicyStore/ObjectSet/Database Collation__ObjectSet/TargetSet/Server_/Database/TargetSetLevel/Server_/Database /PolicyStore/ObjectSet/Database Collation__ObjectSet/TargetSet/Server_/Database Server/Database Database