Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am creating app where user can save options
witch one is better?
to save into user table varchar feeld smthing like (‘1,23,4354,34,3’)
query for this is select * from data where CHARINDEX ( ‘L’, Providers , 0 ) > 0
create other table where user options are and just add rows
select * from data where Providers in (select Providers from userdata where userid=100)
thanks for help
If ever possible, try to avoid putting stuff into comma-delimited strings and then force SQL Server to have to parse all those entries again.
So in your case, I’d definitely go with option two – use a separate table, and let your user’s options be persisted into that table as individual rows. That’s the much cleaner and much more SQL Server-like solution, and if you handle it properly, it will also perform much better (since retrieving data from tables it SQL Server’s core job and competency – parsing strings is not).