https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/170639&feed=atom&action=history
Microsoft KB Archive/170639 - Revision history
2024-03-29T12:13:20Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/170639&diff=89929&oldid=prev
3155ffGd: importing KB archive
2020-07-18T15:35:20Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB170639"></span>BUG: Load Table May Fail If Created with Different ANSI_PADDING =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 170639<br />
<br />
Article Last Modified on 10/3/2003<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft SQL Server 6.5 Standard Edition<br />
<br />
<br />
-----<br />
<br />
<div class="notice_section"><br />
<br />
This article was previously published under Q170639<br />
<br />
</div><br />
<div class="notice_section"><br />
<br />
BUG #: 17012 (NT: 6.50)<br />
<br />
</div><br />
<div class="symptoms_section"><br />
<br />
== SYMPTOMS ==<br />
<br />
An attempt to load a table may fail with the following error message:<br /><br />
<br />
<div class="errormessage"><br />
<br />
Msg 8412, Level 16, State 3<br /><br />
Schemas differ between source table '' and target table 'load_test'.<br /><br />
Table load has been aborted for table 'load_test'.<br />
<br />
</div><br />
<br /><br />
This problem occurs if both of the following conditions are true:<br /><br />
<br />
* The table has a nullable char or varchar column and was created under one ANSI_PADDING setting.<br />
* The table was dumped, dropped, and re-created from a script, but with a different ANSI_PADDING option set.<br />
<br />
Notice in the error message that the State is 3 in this scenario. Other state values indicate true schema differences between the source and destination tables.<br /><br />
<br /><br />
The above behavior will most commonly be seen if the following sequence of events has occurred:<br /><br />
<br />
# An ODBC-based tool, such as the Microsoft Access Upsizing Wizard, is used to originally create the tables<br />
# The schema is scripted using SQL Enterprise Manager and used to re-create the table at a later point in time from a DB-Library based client application (such as ISQL or ISQL/w). ODBC applications set ANSI_PADDING on by default, whereas DB-Library clients do not typically have this option set.<br />
<br />
<br />
</div><br />
<div class="workaround_section"><br />
<br />
== WORKAROUND ==<br />
<br />
When re-creating the table, add an explicit call to SET ANSI_PADDING ON or OFF as appropriate. If the table was originally created from an ODBC client and you are trying to re-create it from a DB-Library client, set the option ON. If you are trying to do the reverse, set the option to OFF.<br />
<br />
</div><br />
<div class="status_section"><br />
<br />
== STATUS ==<br />
<br />
Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.<br />
<br />
</div><br />
<br /><br />
<br />
Additional query words: script schema DMO ::Script<br />
<br />
Keywords: kbbug kbprogramming kbusage KB170639<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd