<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development on Rudi Bruchez</title><link>https://www.pachadata.com/en/docs/howtos/dev/</link><description>Recent content in Development on Rudi Bruchez</description><generator>Hugo</generator><language>en</language><atom:link href="https://www.pachadata.com/en/docs/howtos/dev/index.xml" rel="self" type="application/rss+xml"/><item><title>Fix collation problems on a database</title><link>https://www.pachadata.com/en/docs/howtos/dev/collation-conflict/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.pachadata.com/en/docs/howtos/dev/collation-conflict/</guid><description>&lt;p&gt;If you restore a database onto a server whose default collation is different, two problems can arise:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;collation conflicts in cross-database queries that compare &lt;code&gt;CHAR&lt;/code&gt; or &lt;code&gt;VARCHAR&lt;/code&gt; columns, in a join clause for instance;&lt;/li&gt;&#10;&lt;li&gt;collation conflicts in code that works with temporary tables.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="fixing-the-temporary-table-problem"&gt;Fixing the temporary table problem&lt;/h2&gt;&#10;&lt;p&gt;When you create a temporary table — a table whose name starts with &lt;code&gt;#&lt;/code&gt; — the collation of its &lt;code&gt;CHAR&lt;/code&gt; and &lt;code&gt;VARCHAR&lt;/code&gt; columns comes from the default collation of the &lt;code&gt;tempdb&lt;/code&gt; database. If you then compare those columns with columns from the current database, you get error 468: &lt;code&gt;Cannot resolve the collation conflict between...&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>