SQL Server Performance Forum – Threads Archive
_bstr_t data type length problem
Did anyone have problem with this type of data type?It is reported that when the system is heavily loaded
and sqlserver is running like crazy, _bstr_t (returned
from ADO RecordSet) max it to 500 characters.
What was the error?
Not able to assess from initial question. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com
There is no error – that is even more scary!
just truncated anything beyond 500 chars.
quote:Originally posted by satya
What was the error?
Not able to assess from initial question. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com
Not able to assess from initial question. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com
What was the connection string used?
How do you control data import/export. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com
Does it have anything to do with the conn string? Here is what we do:<br />…<br />sprintf(connStr, "Provider=SQLOLEDB;Data Source=%s;Initial Catalog=myDatabase;<br />User Id=%s<img src=’/community/emoticons/emotion-4.gif’ alt=’;P’ />assword=%s;", dbServer.c_str(), userId.c_str(), password.c_str());<br />myConnPtr->Open(_bstr_t(connStr.c_str()), "", "", NULL);<br />…<br /><br />I suspect there is a problem when the column myColumn length > 500,<br />string value = (string)(_bstr_t)RecordSetPtr->GetCollect(myColumn.c_str()) ;<br />will truncate anything beyound 500 chars.<br /><br /><blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by satya</i><br /><br />What was the connection string used?<br />How do you control data import/export.<br /><br />_________<br />Satya SKJ<br />Moderator<br />SQL-Server-Performance.Com<br /><br /><hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
]]>