G
Guest
The documentation from M'soft for the limits on SQL Server DataBase is:
"SQL Server can have as many as two billion tables per database and 1,024
columns per table. The number of rows and total size of the table are limited
only by the available storage. The maximum number of bytes per row is 8,060.
If you create tables with varchar, nvarchar, or varbinary columns in which
the total defined width exceeds 8,060 bytes, the table is created, but a
warning message appears. Trying to insert more than 8,060 bytes into such a
row or to update a row so that its total row size exceeds 8,060 produces an
error message and the statement fails."
I have a database that has large binary fields representing images that far
exceeds the 8060 bytes per row but yet I don't get an error...why is this?
"SQL Server can have as many as two billion tables per database and 1,024
columns per table. The number of rows and total size of the table are limited
only by the available storage. The maximum number of bytes per row is 8,060.
If you create tables with varchar, nvarchar, or varbinary columns in which
the total defined width exceeds 8,060 bytes, the table is created, but a
warning message appears. Trying to insert more than 8,060 bytes into such a
row or to update a row so that its total row size exceeds 8,060 produces an
error message and the statement fails."
I have a database that has large binary fields representing images that far
exceeds the 8060 bytes per row but yet I don't get an error...why is this?