sql server - How to split string using delimiter char using T-SQL? -

-

i have long string in 1 of columns of table. want specific information:- table structure:-

col1 = '123' col2 = 'aaaaa' col3 = 'clent id = 4356hy|client name = b b bob|client phone = 667-444-2626|client fax = 666-666-0151|info = inf8888877 -mac333330554/444400800'

my select statement is:-

select col1, col2, col3 table01

but in col3 need 'client name's value 'b b bob'.

in col3 -

  • column delimiter '|' pipe char (eg. 'client id = 4356hy')

  • key value delimiter ' = ' equal sign 1 white space (leading , trailing).

please help.

for specific data, can use

select col1, col2, ltrim(rtrim(substring(     stuff(col3, charindex('|', col3,     patindex('%|client name =%', col3) + 14), 1000, ''),     patindex('%|client name =%', col3) + 14, 1000))) col3 table01

edit - charindex vs patindex

test

select col3='clent id = 4356hy|client name = b b bob|client phone = 667-444-2626|client fax = 666-666-0151|info = inf8888877 -mac333330554/444400800' t1m master..spt_values cross join master..spt_values b a.number < 100 -- (711704 row(s) affected)  set statistics time on  dbcc dropcleanbuffers dbcc freeproccache select a=charindex('|client name =', col3) #tmp1 t1m drop table #tmp1  dbcc dropcleanbuffers dbcc freeproccache select a=patindex('%|client name =%', col3) #tmp2 t1m drop table #tmp2  set statistics time off

timings

charindex:   sql server execution times (1):    cpu time = 5656 ms,  elapsed time = 6418 ms.  sql server execution times (2):    cpu time = 5813 ms,  elapsed time = 6114 ms.  sql server execution times (3):    cpu time = 5672 ms,  elapsed time = 6108 ms.  patindex:   sql server execution times (1):    cpu time = 5906 ms,  elapsed time = 6296 ms.  sql server execution times (2):    cpu time = 5860 ms,  elapsed time = 6404 ms.  sql server execution times (3):    cpu time = 6109 ms,  elapsed time = 6301 ms.

conclusion

the timings charindex , patindex 700k calls within 3.5% of each other, don't think matter whichever used. use them interchangeably when both can work.


Comments

Post a Comment

Popular posts from this blog

Javascript line number mapping -

-
magically formatted comments change reported line number of javascript errors in browsers; this: //@line n "f" n line number , f file name. unfortunately, //@line appears ungoogleable. know there documentation on feature, , browsers support it? (i found references here , here .) from can find available in mozilla based browsers. it using js_setoptions command can turn these options on or off depending on values passed. https://developer.mozilla.org/en/js_setoptions
Read more

c# - Is it possible to remove an existing registration from Autofac container builder? -

-
something along lines: builder.registertype<mytype>().as<itype>(); builder.registertype<mytype2>().as<itype>(); builder.deregistertype<mytype>().as<itype>() var container = builder.build(); var types = container.resolve<ienumerable<itype>>(); assert.istrue(types.count == 1); assert.istrue(types[0].gettype == typeof(mytype2)); scenario: go through bunch of assemblies , go register types want make sure have 1 implementation of given type. need before create container. track on own nice if autofac me bit. this cannot done directly using containerbuilder , unless start on new one. mind you, having first built container should able construct new container filtering away unwanted types , reusing registrations first container. this: ... var container = builder.build(); builder = new containerbuilder(); var components = container.componentregistry.registrations .where(cr => cr.activator.limittype != typ...
Read more

php - Mysql PK and FK char(36) vs int(10) -

-
i have read mysql can handle indexes , searches better if tables keys integers rather char(36) uuid's. is worth converting int(10)? note: use 1 server , have have plans use multiple databases concurrently therefore removing 1 of big reasons using uuid. our tables innodb if makes difference. thanks in advance. usually rdbms can handle integer keys pk more efficient, other datatypes. reason how build index column, yes: long dont require string (or other typed) keys, should use integers. however: char(36) , int(10) far away being equal, because int(10) much smaller, char(36). dont know, if require many different keys, should keep in mind. update, complete last paragraph: int(10) 32-bit, char(36) 36 - ^byte^ (= 288-bit). not mean, int consumes less space, means, char(36) has 4 times more different keys.
Read more