Viewing 15 posts - 51,091 through 51,105 (of 59,091 total)
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
You're on the right track... you may have to add extra criteria in the WHERE clause to narrow down the correct matches.
Looks like you're using a native tool to write...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 9:44 am
thelabwiz (4/15/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 7:09 am
Heh... nice try... obviously, you didn't try the code you sent me... there are over 12 errors, the columns in Table2 are out of order with the data, and there...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 7:04 am
If it's a "human" client, then there's no way they need 92,000 rows... that's a lot of pages to read. Normal typewritten pages only has 60 rows by 80...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 6:19 am
... perfect... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 6:12 am
GilaMonster (4/15/2008)
Jeff Moden (4/14/2008)
Steve, do you have a URL handy to sign up?https://www.sqlpass.org/Summit2008/Pages/default.aspx
Are you planning on going this year?
More correctly stated, I'm "Planning on Planning"... Although my plane ticket certainly...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 6:08 am
Heh... ok... thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 15, 2008 at 6:03 am
Viewing 15 posts - 51,091 through 51,105 (of 59,091 total)