June 3, 2010 at 1:28 am
The table '#Source' has been created but its maximum row size (8072) 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. [SQLSTATE 01000] (Message 1708)
may i know the reasone behind the cause?
June 3, 2010 at 2:14 am
It is a warning message, it occurs as row size of your temp table is grater than the size of the maximum row size.
If you can post the temp table creation script it is to give solution.
Have a look at this article
http://www.sqlservercentral.com/articles/Development/2862/[/url]
Nag
Nag
------------------------------------------------
How to get the best help on a forum
http://www.sqlservercentral.com/articles/Best+Practices/61537
June 3, 2010 at 3:33 am
You generally want to avoid tables with such (potentially) large rows. Consider defining sensibly-sized variable-length columns, rather than just picking a huge number.
The warning is 2000-specific: this won't cause an error in 2005 onward, but it will still make a mess of your table structure and can produce very slow read performance.
See:
Managing Space Used by Objects (SQL Server 2000)
Managing Space Used by Objects (SQL Server 2005 onward)
Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply