Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error while altering a table - maximum row size exceeds Expand / Collapse
Author
Message
Posted Monday, October 13, 2008 5:13 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 14, 2008 4:03 AM
Points: 4, Visits: 11
Hi,

I am trying to delete one column from my table using ALTER statement and the following is the SQL statement.

alter table scTabForm0 drop column DataCaptureAutoTaggingXML

But i got the following error

Warning: The table 'scTabForm0' has been created but its maximum row size (18248)
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.


Please help me out from this bug.

Thanks in advance.

Regards,
Hema,
Post #584789
Posted Monday, October 13, 2008 5:22 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Monday, September 30, 2013 2:09 AM
Points: 3,131, Visits: 1,058
Check the following link

http://www.sqlservercentral.com/Forums/Topic212912-169-1.aspx



Post #584797
Posted Monday, October 13, 2008 5:29 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 14, 2008 4:03 AM
Points: 4, Visits: 11
I checked the above link and tried this

Select SUM(C.Length) as Length from dbo.SysColumns C where C.id = object_id('ScTabForm0')

I got the grid values as - 17876.

Please justify the case and explain me the solution.

Many thanks
Hema
Post #584802
Posted Monday, October 13, 2008 5:36 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, March 13, 2014 5:49 AM
Points: 1,391, Visits: 608
run the following DBCC commands:

DBCC CHECKDB
DBCC CHECKTABLE
DBCC CHECKCATALOG
DBCC UPDATEUSAGE

try it, may solve your problem.




Post #584807
Posted Monday, October 13, 2008 5:45 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 14, 2008 4:03 AM
Points: 4, Visits: 11
Hi,

As of now its not working in my server and i don't know how far it is help full to my case.please explain me a bit more.

Thanks,
Hema
Post #584813
Posted Monday, October 13, 2008 11:45 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 14, 2008 4:03 AM
Points: 4, Visits: 11
It will be helpful for me if any body finds the solution.

Thanks
Hema
Post #585210
Posted Wednesday, October 15, 2008 5:27 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, June 9, 2009 1:47 PM
Points: 2,077, Visits: 415
It is only warning. Your table has so many columns (or so big columns) that it si possible you will not be able to store all data by INSERT statement. You can accept this possible danger if you are sure that your INSERT statements never exceed this limitation but can you really? You can avoid this warning by redesign the table. Row size check is done with column definition changes and that is why you have seen this warning when deleting column too. That means you already had this situation before trying to delete column.
Post #586094
Posted Wednesday, October 15, 2008 8:37 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:58 PM
Points: 42,466, Visits: 35,532
hemakrmmc (10/13/2008)

Please help me out from this bug.



It's not a bug. It's a warning that your table's too wide. The max size of a row in SQL server is 8060 bytes. Your table has a maximum possible row size of much larger. If you try to insert a row that's bigger than 8060 bytes, the insert will fail.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #586269
Posted Thursday, October 11, 2012 12:13 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, July 24, 2014 4:11 AM
Points: 853, Visits: 787
run
DBCC CLEANTABLE (0,[table])


Ian Cockcroft
MCITP BI Specialist
Post #1371225
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse