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 |
|
royv
Constraint Violating Yak Guru
455 Posts |
 Posted - 2002-09-27 : 13:18:03
|
| I have been tasked to build a resume database. After hearing some of the issues with using the ntext or text datatypes, I am inclined to stay away from them. I was thinking of breaking up the text data and storing them as multiple rows in the database. I know this would cause the database to grow extremely big, which I don't like, but I can't think of any other better way to do this. Anyone have any suggestions?*************************Someone done told you wrong! |
|
|
Lavos
Posting Yak Master
200 Posts |
Posted - 2002-09-27 : 13:37:29
|
| Well, it really depends on what you need to store.You could have a table with your regular assortment of details, a table that references the main table that lists "skills" or whatnot of the canidate, and then a third table that has the actual text field. (Or if you really don't want to mess with text fields, it could have a sequence number column and a large varchar column (watch your row byte size limits) to split up the text.)I would suggest learning how to work with text columns, but still keep them in a seperate table to store them away from whatever other info you need.----------------------"O Theos mou! Echo ten labrida en te mou kephale!" |
 |
|
|
|
|
|
Resume database