Viewing 15 posts - 136 through 150 (of 683 total)
It's not all about the OP, you know 🙂
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 12:26 pm
Okay - thanks. I was just checking I wasn't missing something 🙂
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 10:16 am
Jeff Moden (5/1/2008)
And, yeah... you could call it "Numbers"... but I'm one of those old guys where the table name shouldn't be a plural... :hehe:
I knew I'd get that response...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 9:37 am
I prefer a table name of 'Numbers' or 'Integers' - and I like to use 'i' for the column name (for integer).
It's all much of a muchness really.
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 9:10 am
Q (5/1/2008)
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 9:02 am
Grant Fritchey (5/1/2008)
RyanRandall (5/1/2008)
I'm also reminded of this article...http://www.sqlservercentral.com/articles/Advanced/lookuptablemadness/1464/
Yeah, that was the one I meant when I said "MUD" but it's supposed to be "MUCK."
:hehe:
Where there's muck, there's mud......
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 8:50 am
Jeff Moden (5/1/2008)
... INTO dbo.JBMTest
I like the idea of a generic multi-purpose test table 🙂
I will be steeling that idea 😀
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 8:48 am
I'm also reminded of this article...
http://www.sqlservercentral.com/articles/Advanced/lookuptablemadness/1464/
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 8:32 am
There are several discussions on this already on the web. Here's one...
http://www.sqlservercentral.com/articles/T-SQL/61244/
The article is poor, but the discussion is useful.
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 8:29 am
Try something like this...
declare @t table (a varchar(10), b varchar(200), c varchar(10))
insert @t
select 'Mut1', 'AZ5397UA9,AZ539CYK2,AZ54022Z3,AZ8040BQ1,AZ0442BB0,AZ2404AW1,AZ307TAD0,AZ442FAE8,AZ442FAQ1,AS490FAV1', 'Credit1'
union all select 'Mut1', 'B5397UB9,B539CYK2,B540223,B8040BQ1,B0442BB0,B2404BW1,B307TBD0,B442FBE8,B442FBQ1,BS490FBV1',...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 8:03 am
Looks good to me, marcelo.
One typo - jo's empid should be 5 rather than 4
All the solutions are how I would (and did :)) do it, depending on the exact...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
May 1, 2008 at 6:06 am
rbarryyoung (4/30/2008)
RyanRandall (4/30/2008)
rbarryyoung (4/30/2008)
...Is this aimed at my suggestion?
Oberion's, I think.
OK - just checking 🙂
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
April 30, 2008 at 11:46 pm
rbarryyoung (4/30/2008)
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
April 30, 2008 at 10:57 pm
Then there's a problem/limitation with the function. I just tested it, and if you change char to varchar it will work...
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
April 30, 2008 at 11:51 am
select * from fn_split(select @facility,',')
Try
select * from dbo.fn_split(@facility,',')
Ryan Randall
Solutions are easy. Understanding the problem, now, that's the hard part.
April 30, 2008 at 11:43 am
Viewing 15 posts - 136 through 150 (of 683 total)