ODBC-Varchar(最大) [英] ODBC - Varchar(max)

问题描述

我们有一些旧版VB6应用程序，它们使用ODBC 13驱动程序以及CST昨天中午前后连接到Azure SQL，突然之间对varchar(max)列的任何读取都导致了垃圾数据.尝试升级到ODBC 17，没有区别.唯一的 起作用的是将varchar(max)更改为varchar(8000).

We have some legacy VB6 applications that connect to Azure SQL using the ODBC 13 Driver and around noon CST yesterday, all of a sudden any reads on varchar(max) columns resulted in garbage looking data. Tried upgrading to ODBC 17, no difference. The only thing that worked was changing varchar(max) to varchar(8000).

这已经工作了几个月，昨天才中午突然停止.有什么变化吗?

This has been working for months, and just suddenly stopped mid-day yesterday. Did something change?

推荐答案

Britishcanuck，您好

Hi Britishcanuck,

您有Azure支持计划吗?如果没有，我可以为您创建一张一次性事件单，以调查此问题.请将您的Azure订阅GUID发送给Microsoft.com上的AzCommunity，我将发回说明以解决此问题 调查.

Do you have an Azure Support Plan? If not, I can have a one-time incident ticket created for you to have this issue investigated. Please send your Azure subscription GUID to AzCommunity at Microsoft.com and I will send back instructions to have this issue investigated.

该服务有滚动更新，因此有可能进行了更新.您知道自己的任何变化吗?

There are rolling updates to the service so it is possible that updates were made. Are you aware of any changes made on your side? 

此致

迈克

这篇关于ODBC-Varchar(最大)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！