row size

I have a vb app that I wrote that saves the info to my SQL database
(SBS2003)
For some reason (my app have been running fine for a couple of months) My
users are getting teh following error when trying to update certain records.
"Can not create a row size of 8436 which is greater than the allowable
maximum of 8060"
What's the deal? How can I fix this?
"johnfli" <john@.here.com> wrote in message
news:OwIiWMp7EHA.936@.TK2MSFTNGP12.phx.gbl...
> I have a vb app that I wrote that saves the info to my SQL database
> (SBS2003)
> For some reason (my app have been running fine for a couple of months) My
> users are getting teh following error when trying to update certain
records.
> "Can not create a row size of 8436 which is greater than the allowable
> maximum of 8060"
> What's the deal? How can I fix this?
You can't. It's an inherent limit of SQL Server.
I'd look at what you're storing. Perhaps you can/need to split the table
into more than one table or move one or more fields to a text field.

>
|||You probably have one or more tables which have varchar columns. The total
lenght of all of the columns in a table can be greater than 8060 as long as
no one actually tries to insert a row which is larger...
For a while no one was adding large rows, now they are...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"johnfli" <john@.here.com> wrote in message
news:OwIiWMp7EHA.936@.TK2MSFTNGP12.phx.gbl...
> I have a vb app that I wrote that saves the info to my SQL database
> (SBS2003)
> For some reason (my app have been running fine for a couple of months) My
> users are getting teh following error when trying to update certain
records.
> "Can not create a row size of 8436 which is greater than the allowable
> maximum of 8060"
> What's the deal? How can I fix this?
>

row size

I have a vb app that I wrote that saves the info to my SQL database
(SBS2003)
For some reason (my app have been running fine for a couple of months) My
users are getting teh following error when trying to update certain records.
"Can not create a row size of 8436 which is greater than the allowable
maximum of 8060"
What's the deal? How can I fix this'"johnfli" <john@.here.com> wrote in message
news:OwIiWMp7EHA.936@.TK2MSFTNGP12.phx.gbl...
> I have a vb app that I wrote that saves the info to my SQL database
> (SBS2003)
> For some reason (my app have been running fine for a couple of months) My
> users are getting teh following error when trying to update certain
records.
> "Can not create a row size of 8436 which is greater than the allowable
> maximum of 8060"
> What's the deal? How can I fix this'
You can't. It's an inherent limit of SQL Server.
I'd look at what you're storing. Perhaps you can/need to split the table
into more than one table or move one or more fields to a text field.

>|||You probably have one or more tables which have varchar columns. The total
lenght of all of the columns in a table can be greater than 8060 as long as
no one actually tries to insert a row which is larger...
For a while no one was adding large rows, now they are...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"johnfli" <john@.here.com> wrote in message
news:OwIiWMp7EHA.936@.TK2MSFTNGP12.phx.gbl...
> I have a vb app that I wrote that saves the info to my SQL database
> (SBS2003)
> For some reason (my app have been running fine for a couple of months) My
> users are getting teh following error when trying to update certain
records.
> "Can not create a row size of 8436 which is greater than the allowable
> maximum of 8060"
> What's the deal? How can I fix this'
>

row size

I have a vb app that I wrote that saves the info to my SQL database
(SBS2003)
For some reason (my app have been running fine for a couple of months) My
users are getting teh following error when trying to update certain records.
"Can not create a row size of 8436 which is greater than the allowable
maximum of 8060"
What's the deal? How can I fix this'"johnfli" <john@.here.com> wrote in message
news:OwIiWMp7EHA.936@.TK2MSFTNGP12.phx.gbl...
> I have a vb app that I wrote that saves the info to my SQL database
> (SBS2003)
> For some reason (my app have been running fine for a couple of months) My
> users are getting teh following error when trying to update certain
records.
> "Can not create a row size of 8436 which is greater than the allowable
> maximum of 8060"
> What's the deal? How can I fix this'
You can't. It's an inherent limit of SQL Server.
I'd look at what you're storing. Perhaps you can/need to split the table
into more than one table or move one or more fields to a text field.
>|||You probably have one or more tables which have varchar columns. The total
lenght of all of the columns in a table can be greater than 8060 as long as
no one actually tries to insert a row which is larger...
For a while no one was adding large rows, now they are...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"johnfli" <john@.here.com> wrote in message
news:OwIiWMp7EHA.936@.TK2MSFTNGP12.phx.gbl...
> I have a vb app that I wrote that saves the info to my SQL database
> (SBS2003)
> For some reason (my app have been running fine for a couple of months) My
> users are getting teh following error when trying to update certain
records.
> "Can not create a row size of 8436 which is greater than the allowable
> maximum of 8060"
> What's the deal? How can I fix this'
>

Rounding Error?

I'm passing a value from an ASP.net app to an sql stored procedure which stores it in a table.

Problem is if, for example, the value is 2.81 the value is ending up as 2.08999... in my table, but if i do say 6.3 it's fine.

Ive tried having the variable in asp and the field where its stored in sql as a number of types but all with the same result.

Any ideas?

Geoff.You should check the definition and precision of your database column.
Maybe change it from float to money.

Regards
Fredrik