I'm running the following code
SET ANSI_WARNINGS OFF
set @sqlAlter = 'alter table #tblQCResults add [' + @TestName + '] nvarchar(30)'
exec (@sqlAlter)
Even after setting warnings off, it still generates this message:
Warning: The table '#tblQCResults' has been created but its maximum row size (8179) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
I understand the message, and it is not a problem. The problem is that I am calling the stored procedure from VB and putting the results in an ADODB recordset. So the warning messages are messing up my recordset.
Anyone have any idea why SET ANSI_WARNINGS OFF is not eliminating these messages?
I've tried
set @sqlAlter = 'SET ANSI_WARNINGS OFF alter table #tblQCResults add [' + @TestName + '] nvarchar(30)'
and it still doesn't stop the warning messages.
Any ideas would be greatly appreciated.
Thanks
SET ANSI_WARNINGS OFF
set @sqlAlter = 'alter table #tblQCResults add [' + @TestName + '] nvarchar(30)'
exec (@sqlAlter)
Even after setting warnings off, it still generates this message:
Warning: The table '#tblQCResults' has been created but its maximum row size (8179) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
I understand the message, and it is not a problem. The problem is that I am calling the stored procedure from VB and putting the results in an ADODB recordset. So the warning messages are messing up my recordset.
Anyone have any idea why SET ANSI_WARNINGS OFF is not eliminating these messages?
I've tried
set @sqlAlter = 'SET ANSI_WARNINGS OFF alter table #tblQCResults add [' + @TestName + '] nvarchar(30)'
and it still doesn't stop the warning messages.
Any ideas would be greatly appreciated.
Thanks