Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
zion99
Posting Yak Master
141 Posts |
 Posted - 2008-08-25 : 10:29:18
|
| Hi,is it possible to increase the size of a table to accomodate as many rows as possible. i have read about vardecimal, but in my case it wont not be useful.Can anybody suggest me an alternative to remove the below warning:Warning: The table "boundary" has been created, but its maximum row size exceeds the allowed maximum of 8060 bytes. INSERT or UPDATE to this table will fail if the resulting row exceeds the size limit |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-08-25 : 10:32:50
|
| Thats just telling that the rowsize is more than allowed size. it wont cause you a problem unless you try to insert really big values into it. Are you having lots of long varchar fields? |
 |
|
|
zion99
Posting Yak Master
141 Posts |
Posted - 2008-08-25 : 10:47:26
|
| yeah... as part of a datawarehousing requirement, i need to collate data of some 25 columns into a single table. |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-08-25 : 11:09:05
|
Snowflake?Normalization or SCD?
E 12°55'05.25"N 56°04'39.16" |
|
|
|
zion99
Posting Yak Master
141 Posts |
Posted - 2008-08-25 : 11:18:23
|
| nothing of that sort atleast for this issue, ...in the SOURCE there is a table1 with column COL1 (primary key). there are other 2 or 3 tables having related data & the same primary key COL1. i m just combining the columns into 1 table in the DESTINATION. sorry for the trouble... sql 2005 doesn't give any warnings about 8060 bytes, but whatever i could read from the web, such a design has an effect on performance.please suggest whether i should continue with one table approach or should i make 2 or 3 tables with related primary key COL1. one issue which i foresee with the second alternative is reports which will run on this multi-tables will have to make a join & that will be slower. |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-08-25 : 11:22:40
|
SQL Server 2005 WILL give you a warning when creating a table that potentially allows you to store more than 8060 bytes per record.DECLARE @Sample TABLE (Col1 VARCHAR(5000), Col2 VARCHAR(5000))Warning: The table '@Sample' has been created but its maximum row size (10025) 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. A warning only.The error may occur later if an inserted record have more than 8060 bytes.
E 12°55'05.25"N 56°04'39.16" |
|
|
|
zion99
Posting Yak Master
141 Posts |
Posted - 2008-08-25 : 11:25:43
|
| surprisingly, i didnt get a warning... i created it again to confirm... my table size is currently 33500 bytes. |
|
|
|
zion99
Posting Yak Master
141 Posts |
Posted - 2008-08-25 : 11:27:39
|
| i guess, some warnings might have been turned off... but i really didnt get any warning..Microsoft SQL Server 2005 - 9.00.3161.00 (X64) Apr 3 2007 11:14:20 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1) |
|
|
|
|
|
|
increasing table boundary