Viewing 15 posts - 18,076 through 18,090 (of 59,102 total)
quagmired (3/19/2016)
Jeff Moden (3/19/2016)
I'm a big fan of using the right tool to the job (even when others don't think it's the right tool). With that in mind, what...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 19, 2016 at 8:11 pm
tarr94 (3/18/2016)
Thanks for the response! I marked it as the correct solution because I know I've seen SSIS used for this purpose, but I actually ended up dumping the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 19, 2016 at 1:11 pm
Mac1986 (3/18/2016)
foreach ($line in $ReturnString)
{
$array = @()
if ($line -notmatch "ID,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 19, 2016 at 12:55 pm
GeorgeCopeland (3/19/2016)
CV is a common business term and it is used extensively in academia. I prefer qualifications brief .
Heh... I refer to both a "CV" (Curricula Vitae) and a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 19, 2016 at 12:42 pm
mburbea (3/19/2016)
I 100% agree with you that his test script wasn't the best. His number table splitter you've already dressed down, and that xml splitter doesn't do any lob caching...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 19, 2016 at 8:17 am
quagmired (3/19/2016)
Jeff Moden (3/18/2016)
quagmired (3/18/2016)
Jeff Moden (3/18/2016)
quagmired (3/17/2016)
Parting thought: how would you match a 1 followed by an arbitrary number of 0s followed by a 1 with T-SQL?
Starting thought.... Have...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 19, 2016 at 7:12 am
mburbea (3/18/2016)
Also sqlperformance article seems to suggest the thing performs fairly well...http://sqlperformance.com/2016/03/t-sql-queries/string-split
Obviously, his t-sql and xml based splitters are poor choices.
Whomever wrote the numbers table splitter doesn't have a clue...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 11:03 pm
quagmired (3/18/2016)
Jeff Moden (3/18/2016)
quagmired (3/17/2016)
Parting thought: how would you match a 1 followed by an arbitrary number of 0s followed by a 1 with T-SQL?
Starting thought.... Have you ever actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 9:57 pm
Jeff Moden (3/18/2016)
quagmired (3/17/2016)
Parting thought: how would you match a 1 followed by an arbitrary number of 0s followed by a 1 with T-SQL?
Starting thought.... Have you ever actually had...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 9:30 pm
Matt Miller (#4) (3/18/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 9:14 pm
Luis Cazares (3/18/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 8:17 pm
Goldie Lesser (3/18/2016)
Ed Wagner (3/17/2016)
If it doesn't have a sequence number, I wont be using it. 'Nuff said.
I use Jeff's function all the time, and I can't even think...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 3:27 pm
Eirikur Eiriksson (3/18/2016)
mburbea (3/18/2016)
http://www.sqlservercentral.com/Forums/FindPost1570980.aspx
Paul White (5/14/2014)
If so, you might not be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 3:06 pm
mburbea (3/18/2016)
http://www.sqlservercentral.com/Forums/FindPost1570980.aspx
Paul White (5/14/2014)
If so, you might not be testing what...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 3:05 pm
quagmired (3/17/2016)
Parting thought: how would you match a 1 followed by an arbitrary number of 0s followed by a 1 with T-SQL?
Starting thought.... Have you ever actually had to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2016 at 1:39 pm
Viewing 15 posts - 18,076 through 18,090 (of 59,102 total)