Viewing 15 posts - 42,661 through 42,675 (of 59,102 total)
If I may suggest, you don't need to join to the same table 4 times to do this. If you had 50 such columns, that would make for some...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 8:39 pm
pat (7/31/2009)
Hi all i have data in date column likejul 5 2009 12:00 AM but i need to have result like 07/05/2009 with no time.
How can i do that.
Thanks
What will...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 8:10 pm
Yes... one works on the TEXT datatype and the other doesn't. Please refer to Books Online for details.... Books Online comes free with SQL Server.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 8:08 pm
NP... when I wrote it, it seemed crystal clear to me. Looking back at it, it's not so clear.
You have had a bit of a tough go this week...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 8:02 pm
Sounds like interview questions... if I answer correctly, do I get the job?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 7:58 pm
Lynn Pettis (7/31/2009)
How many times do you plan on posting this???Multiple post, please post responses here.
Heh... not to worry, Lynn. It would appear that a good number of folks...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 7:53 pm
Heh... Gail took the words right out of my mouth.
Post your code and let's have a look-see.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 7:51 pm
What do you mean by a single "attribute"? Do you mean it's all a single string to begin with?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 7:50 pm
Sorry, Scott... I've got nothing for you on this. My response will serve to "bump" your question again and your question gives me yet another reason to avoid CLR's....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 7:44 pm
apat (7/31/2009)
Thanks for the help... it worked...
It worked? Which of Rupashri's SSIS suggestions worked?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 7:33 pm
Jack Corbett (7/31/2009)
With...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 7:23 pm
Matt Wilhoite (7/31/2009)
Here is what I did. There is probably a better way but this was the first thing that came to mind.
Nice... the optimizer is also smart enough...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 6:54 pm
Allister Reid (7/31/2009)
here is a solution that relies on a tally table http://www.sqlservercentral.com/articles/T-SQL/62867/ and is based upon the code in http://www.sqlservercentral.com/articles/Crosstab/65048/, these are two excellent articles, and I recommend them...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 6:31 pm
Heh... whatever you do, remember what the old password was so you can reuse it if all hell breaks loose. 😛 Yeah... I know... how obvious can I be?...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 6:29 pm
balbirsinghsodhi (7/31/2009)
Wish, I had three eyes, looks like two eyes are not enough.Thanks guys.
Heh... that's why I wear glasses... it sometimes takes "four eyes". 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 6:23 pm
Viewing 15 posts - 42,661 through 42,675 (of 59,102 total)