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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-04-20 : 10:00:10
|
| Zack writes "Greetings,For the application I'm working on now I need to import a fixed length string of 895 characters. Each character in the string represents some value.Am I better of importing all 895 characters into a single db field or should I create 895 single character fields in the db table?When I use the data I will not be interested in all 895 values at once. Possibly only a single value or a small subset of all values.Does it matter which approach I take? FWIW, I'm leaning towards the single 895 character string option...Thanks in advance for your advice!Take Care,Zack Jones" |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-04-20 : 23:11:39
|
| ???? Are they actually 895 seperate values? Or do you have for example: 1-5 = name6-15 = addressetc, etc?What percentage of the time will you be using all of them? What are you going to do with them?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
DustinMichaels
Constraint Violating Yak Guru
464 Posts |
Posted - 2004-04-20 : 23:39:42
|
| It seems like you need to normalize your database.Having a single column of a table which holds multiple values makes your table not even in first normal form.Why don't you post what you plan to do with the information in the column. Maybe someone can help you normalize your design.Dustin Michaels |
|
|
|
|
|
|
Dealing with 895 Character String