How do I parse column values into dynamic/static columns

Question

1.00/5 (1 vote)

See more:

I split the column name: Data into 200 static column .and its working .Now I have one challenge that i want parse that particular values into respective column number
For example :

data	data1	data2	data3
1___39300346.1638873276,75___not logged-in	1___39300346.1638873276	75___not logged-in

i want parse

75___not logged-in

the values into column number 75 i.e columnname:data75

like

1___39300346.1638873276

parse thes value into column number i.e coulmnname:data1

could you please help on that ?

What I have tried:

tried to apply string function/tvf/char index

Posted 17-Jan-22 20:20pm

siddhesh bhavar

Updated 17-Jan-22 22:08pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2022-01-17T22:08:00

The best advice I can give you is simple: don't.

SQL string handling is at worst primitive, and at best poor because it's a data storage and retrieval language, not a data processing language. It's excellent at storing and retrieving data based on the relationships between data items and the filters / criteria you provide to reduce or aggregate the data - but it's it not designed for data processing.

That's what presentation languages are there for: getting input, manipulating it into a "sensible form" and passing it to the DB ready for storage - and that's why presentation languages have better string manipulation functions, regular expression support, data checking and conversion functions and SQL doesn't.

Do all that in your presentation language, and it will produce better code, that is much easier to maintain and understand. It's possible in SQL, but when a mod comes along in two months time because of a condition you didn't think of it's going to be an impenetrable mess of SQL code to try and change to accommodate it!