Viewing 15 posts - 42,871 through 42,885 (of 59,063 total)
Maybe it's just a bit late for me but I'm thinking you're going to have to explain the mapping on that one just a wee bit more than you have....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 12:42 am
AShehzad (7/19/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 12:37 am
Shuaib (6/25/2009)
I have a comma delimited values and I want to split this values into mulitple columns. Can someone share the idea / scripts?
Ex
Input
@v-2 = 'A,B,C'
Output
Col1 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 12:10 am
ab5sr (6/25/2009)
I'd look at the split method in .Net to create an array for this. Otherwise you might get stuck with some cheesy TSQL string manipulation.
I know this is an...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 12:06 am
ps (6/22/2009)
Well, Jeff's queries are like that, Rocket speed execution. 😀
:blush: Thanks, Pradeep. :blush: That's an awfully nice compliment especially coming from someone like you.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2009 at 12:02 am
So I say to the doctor, "Doc, when I hold my arm up like this, it hurts." Doctor says, "So don't do that."
Being that this is SQL Server 2000...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:56 pm
Ummmmm.... be careful folks. If you don't run DBCC UPDATEUSAGE(0), you can get some seriously incorrect information. I'll try not to bad mouth the cursor/loop solutions on this...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:47 pm
Lookup "Expanding Hierarchies" in SQL Server 2000 Books Online.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:25 pm
Provided that you will always have a 2 digit month and a 2 digit year, all you have to do is flip the MMYY to YYMM, add the DD part...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:23 pm
Thought I'd "bump" this for you... do you still need help on this?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:11 pm
Edward (7/14/2009)
Yep we are filling the gaps as we are reaching the min/max integer barriers.
Save yourself and others the pain... simply switch the column datatype to BIGINT. You will...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:09 pm
It's simple but no one ever answers my questions once I give an answer. With that in mind, please explain the business reason for wanting to do this. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 11:01 pm
WayneS (7/8/2009)[hrSo, just to make sure I have it correct, I should have used
from #tblTest with (TABLOCKX) OPTION (MAXDOP 1)Correct?
Correct. Man... sorry... I got way behind...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:58 pm
karthikeyan (7/9/2009)
Greg,They will pass it as STRING.
Why i need like this?
I have a table called country_exposure
create table country_exposure
(
Fund_Id int,
Malaysia decimal(16,8),
Philippines decimal(16,8),
Taiwan decimal(16,8),
Thailand decimal(16,8),
India decimal(16,8),
Austria decimal(16,8),
Belgium decimal(16,8),
Denmark decimal(16,8),
Finland decimal(16,8)
)
Really, really bad...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:54 pm
See the following for an answer...
http://www.sqlservercentral.com/articles/Test+Data/61572/
And please stop double and triple posting.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 19, 2009 at 10:50 pm
Viewing 15 posts - 42,871 through 42,885 (of 59,063 total)