The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

multiple ntext?

Hi there,
Am using Sql Server 2000. I'm having problems with a db which has 7 text fields, 5 are varchar and 2 are ntext. The problem, the data that needs to be stored in a record seems to be exceeding the row limit. If I changes all fields to (n?)text instead of varchar, would that be ok or is that bad, inefficient, will cause timeouts etc?

Thanks. I was just trying to get a general idea of whether it would be considered bad design to have many ntext fields in one table. I've been having some issues with the amount of data I need to store in a row and was considering storing all of it in multiple ntext fields, and decided to see whether this was known to be bad db design.