FIX: You notice additional random trailing character in values when you retrieve the values from a fixed-size character column or a fixed-size binary column of a table in SQL Server 2005
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
In SQL Server 2005, when you retrieve values from a fixed-size character column or a fixed-size binary column of a table, you notice additional random trailing characters in the values.
This problem occurs when all the following conditions are true:
The table is populated with the values in the connection context that has the ANSI_PADDING setting set to OFF.
The values with which the table is populated are returned by an ISNULL function from a SELECT statement. The SELECT statement has the following characteristics:
The SELECT statement has an INTO clause that creates the table. Additionally, the table is created in a connection context that has the ANSI_PADDING setting set to OFF.
The SELECT statement has an OUTER JOIN of TableB and TableC on their fixed-size binary columns or fixed-size character columns.
The fixed-size binary column or fixed-size character column values of either TableB or TableC that contain one or more NULL values are passed to the first parameter of the ISNULL function.
The table column that is passed to the first parameter of the ISNULL function is nonnullalble.
The second parameter of the ISNULL function is a constant value. The constant value has the smaller length than the fixed-size character column length or the fixed-size binary column length of the table in which you experience this problem.
Note TableB and TableC are used in this section to differentiate from the table in which you experience the problem.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
The original release version of SQL Server 2005-based hotfix requires the original release version of SQL Server 2005.
The SQL Server 2005 SP1-based hotfix requires SQL Server 2005 SP1.
For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for SQL Server 2005
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
The original release version of SQL Server 2005-based hotfix
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
Back to the top
