Viewing 15 posts - 46,831 through 46,845 (of 59,095 total)
I solved a post, last night, using the SIGN function instead of CASE for a pretty good performance gain. It reminded me of what my original programming mentor taught...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2008 at 3:59 pm
ishaan99 (12/3/2008)
Thanks Guys i used the charindex without sign function to resolve this. Thanks for everybody;s input.
You bet... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2008 at 3:50 pm
Bob Hovious (12/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2008 at 3:49 pm
mlandry (12/3/2008)
Whoa, using SQL to do cross-tabs really is "old school" (circa mid-90's or before.) It just wasn't designed for this.
Do yourself a BIG favor and try Analysis Services....
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2008 at 9:41 am
ggraber (12/3/2008)
Great article Jeff!Do you think this will perform better than a dynamic pivot?
Thanks for the feedback and absolutely! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2008 at 8:25 am
Thanks for the great feedback Anirban. Great to know that folks get things out of these articles. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2008 at 8:00 am
Chirag (12/3/2008)
Another masterpiece.Small typo -
You have a single quote missing at the end of the date for the code under OLD fashioned swap.
"SET @EndDate = '2008-01-15 "
Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2008 at 5:03 am
Is this what you want?
--===== Declare local files
--Jeff Moden
DECLARE @DBID INT
DECLARE @DBName VARCHAR(30)
DECLARE @Text ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 10:57 pm
fausto usme (12/2/2008)
Hello People,i need to do the next.
Why? What's the goal or business rule other than someone said they wanted it?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 10:52 pm
John Barry (12/2/2008)
Thanks - I have used that syntax as well - it's cool. And I agree if I move the Nextval outside the transaction it would solve the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 10:46 pm
One more thing... you're updating the same columns that you have in your criteria. Sometimes, and it's again unpredictable, that will cause a recompile for every row updated. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 10:42 pm
P.S. You may want to stop that single Update you're running right now. It may take several hours to rollback or it might rollback quicker. But even...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 10:38 pm
To add to what Lynn stated.... there are two reasons you need to break up such a large update... the first is the LOG file. Even with the SIMPLE...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 10:36 pm
That's not really a DateTime datatype you asked for or it would have a date with it like this...
DECLARE @Time CHAR(4)
SET @Time = '1330'
SELECT CAST(STUFF(@Time,3,0,':')...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 7:40 pm
John Barry (12/2/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2008 at 7:27 pm
Viewing 15 posts - 46,831 through 46,845 (of 59,095 total)