SQL 2008 ,SQL 2012 超长SQLBUG - by 漫步者9999

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 773474 Comments
Status Resolved Workarounds
Type Bug Repros 0
Opened 12/4/2012 5:09:37 PM
Access Restriction Public





Location:         memilb.cpp:700

Expression:      cbTransferred <= (ULONG)cbLength && cbTransferred > 0

SPID:              54

Process ID:      1800

消息 3624,级别 20,状态 1,第 1 行

系统断定检查已失败。有关详细信息,请查看 SQL Server 错误日志。通常,断定失败是由软件错误或数据损坏导致的。若要检查数据库是否已损坏,请考虑运行 DBCC CHECKDB。如果您同意在安装过程中将转储发送到 Microsoft,则将向 Microsoft 发送微型转储。更新可能在 Microsoft 的最新 Service Pack 或技术支持部门的 QFE 中提供。 

消息 0,级别 20,状态 0,第 0 行

Sign in to post a comment.
Posted by Microsoft on 1/15/2013 at 1:35 PM
Dear customer,
As we don't have enough information to understand the issue (please, see my ask before), it does not look actionable at our side. I would like to receive more information on the issue/repro, or resolve the issue otherwise.
Thanks. Alexey, SQL Development.
Posted by Microsoft on 12/18/2012 at 4:14 PM
Thanks for reporting your issue.
Could you, please, clarify what exactly you are doing when you are hitting the repro?
I created a database with Chinese_Simplified_Pinyin_100_BIN collation (I don’t understand Chinese but figured out that if I try to use Chinese Simplified encoding and then use Bing Translator to translate, it gives me names that somewhat make sense, so I used the first Chinese Simplified collation available), and then created the schema according SQLQuery4.sql file and trying the insert statement in the text file you attached (running set identity_insert M住院病案_病历列表 on first to allow it to insert an identity value) – it worked just fine for me – the record gets inserted w/out any error messages and I can select it.
Also, it would be helpful if you could attach a memory dump generated by SQL Server. You can find it in the MSSQL\Log subfolder of your SQL Server instance installation, named like SQLDumpXXXX.mdmp.

     Alexey, SQL Development