Viewing 15 posts - 54,691 through 54,705 (of 59,101 total)
The real problem is that you're trying to solve two different problems at once... divide and conquer... the code will not only be faster performance wise, it will also be...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 5:00 pm
I'm by no means making fun of you, Linda... but the polar ice caps are retreating faster than "200 rows per minute" and it's why I don't like things like...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 10:26 am
Matt is correct about needing the CASE... but I'm not sure why we need the #Summary table, at all...
First, a brief lesson in creating massive amounts of test data in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 10:14 am
Perfect... I'll be back...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 9:20 am
Sorry... that just doesn't help me... all of your examples show only one date... would you please do as I ask so I can help? Please change the following...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 9:02 am
To add to that... are there Primary Keys on these tables? Is there a clustered index? Are the tables in a constant state of flux do to inserts,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 8:28 am
If it's the "Estimated" Execution Plan... pay those percentages no mind... it "lies" because it will frequently miss things. For example, only the first pass of a triangular join...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 8:16 am
Heh... thanks for the "apple" ๐
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:42 am
Dunno about your first question but I'm pretty sure that the answer to your second question of can you "view images in SQL Server" is an emphatic "NO".
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:39 am
Heh... flies haven't found it, yet... :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:33 am
Thanks, but doesn't quite tell me what you want... not trying to be difficult here, either but "one picture is worth a thousand words"....;)
You listed this as an "input"...
Insert Into...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:30 am
Yep... I agree with all of that... if it's for GUI code...
For batches, the proc will probably recompile anyway just because the data will have changed enough to need a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:24 am
A big key here is that David DIDN'T even use a function (although you could if it's for RBAR GUI code)... it splits a whole table's worth of information in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2007 at 7:16 am
Heh... I cheat like hell... load up one staging table with everything... delete the dupes with the "earliest" information... flip the pass-through-view to look at the new table... drink beer...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2007 at 8:56 pm
Ramesh Lende (10/8/2007)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2007 at 8:47 pm
Viewing 15 posts - 54,691 through 54,705 (of 59,101 total)