Viewing 15 posts - 42,631 through 42,645 (of 59,102 total)
Ah! Got it. Thanks for taking the time to explain. Heh... it's funny... I knew that could be the case in a single query but I wasn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 12:15 pm
Just from a practical standpoint, the less you select, the fewer bytes need to make it across the pipe, go through implicit conversions, etc, etc. If you don't need...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 11:13 am
Heh... nope. I knew that and I've asked the question incorrectly... What I should have as about the following is...
GilaMonster (8/1/2009)
Jeffrey Williams (7/31/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 10:11 am
Tejas Shah (8/1/2009)
I face this problem in one of my project's reports, so I keep practice to not convert the field.
I actually agree. Formatting dates and times in T-SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 9:46 am
You bet... thanks for the feedback, Ghanta.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 9:34 am
Heh... Don't do it for me... I actually can't help because I use something else instead of SSIS. It was just an observation that even if someone wanted to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 9:31 am
Slow... I guess I'm trying to juggle too many things at one time. I need to concentrate on "one" of something and get it done. The running total/quirky...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 8:49 am
Now that's funny stuff right there... it reminds me of folks that think banging on an elevator button will make the elevator go faster.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 8:46 am
GilaMonster (8/1/2009)
Jeffrey Williams (7/31/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 8:44 am
Hi Pete,
Ok... but there are better ways to do this. I guess I would first question the requirement of making alpha-numeric keys in the first place. An IDENTITY...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 8:39 am
Yep... that should work.
As a side bar, it's been a day or two since this thread has been active and I orginally didn't believe your code would work...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 8:21 am
Checking...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 8:07 am
Nah... sorry. Just passing through. I don't even know how to spell "Service Broker".
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 12:06 am
I thought most reporting programs had date formatters built in?
No matter... here's how to do it in T-SQL... just keep in mind that it won't be "portable" from country to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 1, 2009 at 12:01 am
I guess you've lost me a bit... why do you need this to be dynamic SQL? I believe the example code I posted does everything you've asked.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 31, 2009 at 11:57 pm
Viewing 15 posts - 42,631 through 42,645 (of 59,102 total)