Viewing 15 posts - 51,091 through 51,105 (of 59,098 total)
GSquared (4/16/2008)
Jeff Moden (4/16/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2008 at 1:21 pm
Thanks, Gus... the order was to preserve Asimov's original order and because they can be broken down more simply as "Protect the data, protect the project, protect the user" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2008 at 9:34 am
True enough... you won't always be able to use something like INNER MERGE JOIN because the optimizer doesn't always like it.
Teaching a man to fish... the WITH RECOMPILE option is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2008 at 9:27 am
Dang... I keep forgetting about that... thanks for the reminder, Matt. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2008 at 9:21 am
corey.psychological (4/16/2008)
aaah SPOT ON!!:D:D:D:D:D:D:D:D:D:D:D:D:D
THANKS ALOT FOR THE HELP!!!!!!!
Heh... you did it... you took the time to post some simple table structures and some data. You made my day because...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2008 at 9:16 am
SELECT RateID, CONVERT(CHAR(8),CAST(SUM(CAST(EndTime - StartTime AS FLOAT)) AS DATETIME),108) AS TotalHours
FROM ConsultancyDetails
GROUP BY RateIDYou can't sum the difference between two date times... but...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2008 at 2:13 am
Hey Highway! Don't give up, yet... turn this into a learning experience because Sergiy is correct... no matter where you go, you're going to run into steaming piles of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 16, 2008 at 1:22 am
Whoa... wait a minute... back the performance pony up! Let's review the facts...
1. escaleraroyal already stated that the vendor tested it in QA and it was slow...
2....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 6:05 pm
Corey,
This looks a bit like homework, and we don't mind helping with that because you tried on question 1.
We need just a bit more information...
In the first...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 5:52 pm
Your co-worker is, well... wrong! Even if you had the best indexing in the world on all the tables, updating 18 million rows with new data for the new...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 5:09 pm
If you do this with a trigger, the INSERT trigger table will have all the rows that changed in it... automatically...
... then , the trigger could insert into the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 5:01 pm
Sean... take a look at Books Online... most of the examples given are just flat wrong... for example...
[font="Courier New"]SELECT @COL = CASE @Section
...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 4:58 pm
samiam914 (4/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 4:45 pm
terrence_daniels (4/15/2008)
thanks I am looking into Books online...but my question is why is the script looping through the tables? 😉
If you're looking at the execution plan and seeing the loop,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 4:40 pm
Can the data generator code you provided be used to generate that many rows? I'd like to "play" some more because 41 to 45 seconds to produce "36820...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 9:53 am
Viewing 15 posts - 51,091 through 51,105 (of 59,098 total)