Viewing 15 posts - 42,151 through 42,165 (of 59,067 total)
Elliott W (8/26/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2009 at 1:51 pm
Steve Jones - Editor (8/29/2009)
Tune us an OS server on a core installation, and also improve the language. I bet some of your items...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2009 at 1:43 pm
That might be nice but I'd rather see them spend the time on improvements to SQL Server itself. For example... some better IO functions for T-SQL. Why is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2009 at 1:20 pm
You are not alone... it's in our blood and nature to do all the things you mentioned.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2009 at 1:03 pm
MANU (8/28/2009)
Try:UPDATE tablename
SET columnname= REPLACE(SUBSTRING(columnname, 1, DATALENGTH(columnname)), char(13), '')
WHERE charindex(char(13) , columnname) > 0
HTH!
MJ
Manu,
Just curious... Why are you using SUBSTRING in this? REPLACE...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2009 at 7:58 pm
Roy Ernest (8/28/2009)
Alvin, This is a dream start for us. The island I reside in has only 100,000 people in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2009 at 7:38 pm
Garadin (8/28/2009)
I'll second the props to Jeff for learnin' me all about Tally tables.
Heh... thanks, Seth. Folks like you, Bob, and a couple of others have made it a...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2009 at 6:26 pm
Lynn Pettis (8/28/2009)
If I am right, this should work:
DECLARE @jdate int
SET @jdate = 109252
select dateadd(dd, (@jdate - ((@jdate/1000) * 1000)) - 1, dateadd(yy, @jdate/1000, 0))
That's more like it... and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2009 at 9:45 am
Ummmm... won't that offset number work only for 2009?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2009 at 9:07 am
Heh... spot on Gus. I pretty much agree with all of that. I'd still like to know why folks would want to use TempDB instead of a "utility"...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 28, 2009 at 8:52 am
schauhan13 (8/27/2009)
in my table there is clumnJdate int
In this column julian date is stored
now i need to convert it into standard date. Can anyone help me please
At least...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2009 at 9:17 pm
jim.rasmussen (8/27/2009)
I have found a solution. Thanks for the help.Jim
2 way street here, Jim. Please post the solution you found. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2009 at 9:14 pm
Gianluca Sartori (8/27/2009)
And this is the main reason why I like temp tables: it's all mine and I can do whatever I want with...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2009 at 8:17 pm
Dean Jones (8/27/2009)
If 2 instances are trying to read data off the table, I dont see anything that will go wrong here. please explain
See the post just above this one,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2009 at 8:12 pm
GSquared (8/27/2009)
Jeff Moden (8/27/2009)
I think it's a bad idea because what will happen if two instances of your code are executed at the same time?
That's why I mentioned checking for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 27, 2009 at 8:08 pm
Viewing 15 posts - 42,151 through 42,165 (of 59,067 total)