Viewing 15 posts - 47,566 through 47,580 (of 59,095 total)
Thanks for the "cover". 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 5:49 pm
Man, would I like to be able to comment here on external articles so I don't have to sign up for every forum that has a "dangerous code" article. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 11:59 am
rishgup (10/26/2008)
Jeff Moden (10/26/2008)
And, how does the app know what that latest value is?Whenever any Insert Operation occurs on tbl employee counter_ins will be increment by 1.
Heh... yeah, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 6:00 am
Have you looked in "parameter sniffing" like I suggested above?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 5:56 am
Heh... me too... as previously stated, there's just not enough info to help here.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 5:55 am
Not without actually putting my hand on the system and not with my hands tied by rules like not being able to change code which is likely the biggest performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 5:52 am
Peso (10/27/2008)
Also seehttp://www.sqlteam.com/forums/topic.asp?TOPIC_ID=112721
http://www.sqlservercentral.com/Forums/Topic562564-338-1.aspx
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3829716&SiteID=1
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3928920&SiteID=17
Heh... but the question remains... has anyone done it correctly, yet?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 5:48 am
AnzioBake (10/27/2008)
I just tested this again and even explicit conversion gives the result as in Jeffs first example. I played some more and it appears...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 27, 2008 at 5:21 am
paulneyman (10/26/2008)
Jeff Moden (10/25/2008)
It would help us give you a better answer quicker if you posted Table A and it's data in a readily "consumable" format. See the link...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2008 at 7:37 pm
And, how does the app know what that latest value is?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2008 at 7:32 pm
pozzo (10/26/2008)
I think I need to be more clear.
I already have a single table for each month in each year.
I need to export each table to Excel...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2008 at 7:25 pm
Garadin (10/25/2008)
rbarryyoung (10/25/2008)
Jeff Moden (10/25/2008)
Parul Sharma (10/24/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2008 at 7:22 pm
Ross McMicken (10/26/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2008 at 7:17 pm
Absolutely no comment on that stupidity.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2008 at 7:13 pm
Bottome line is, don't do calculations on t.N in the WHERE clause or all of the Tally table must be evaluated... as I saw previously suggested, this works the best...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 26, 2008 at 10:28 am
Viewing 15 posts - 47,566 through 47,580 (of 59,095 total)