Viewing 15 posts - 32,956 through 32,970 (of 59,099 total)
bitbucket-25253 (8/7/2011)
Jeff Moden (8/7/2011)
sqlfriends (8/5/2011)
Our production server will be enterprise version
For the license issue, can I just use...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 6:39 pm
@SQLFRNDZ (8/5/2011)
You use developer edition but really depends on what you want test I mean there...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 6:35 pm
I was in the middle of a huge rant on books but see that George and Tom covered some good amount of what I had to say on this subject....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 6:09 pm
Jeff Moden (8/7/2011)
vermarajiv (8/2/2011)
I tried recursive CTE and you are right it does not allow aggregate functions
Based on your tip, I found...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 4:53 pm
GilaMonster (8/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 4:47 pm
gah (8/5/2011)
Another possibility using quirky update.......thoughts anyone please?
I just checked through your QU code, Gah... VERY nicely done! It's not often I see someone follow all the rules especially...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 4:39 pm
eccentricDBA (8/2/2011)
Here is a technique. It would need to be tested for usuability with a large record set.
Done... and I think there may be a problem... it would appear...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 4:26 pm
Jeff Moden (8/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 4:20 pm
vermarajiv (8/2/2011)
I tried recursive CTE and you are right it does not allow aggregate functions
Based on your tip, I found a semi...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 3:51 pm
Nomvula (8/7/2011)
thanks for the response, i realized that i won't be able to get the Max(TimeTo) since the transactions happened on the same date and same time.
i have another...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 3:04 pm
I can't even find anyone that knows the app well that the database supports!
I'd back it up, take it offline, and see who calls for it before I spent...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 3:01 pm
Ben-Gan has some very interesting date-span code that runs like the wind. It would be perfect for this and actually negates the need for a Quirky Update. In...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 2:58 pm
sqlfriends (8/5/2011)
Our production server will be enterprise version
For the license issue, can I just use developer version for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 2:54 pm
Gosh, NO! You shouldn't ever save formatted dates and times in the database. It messes up just about everything and it's a real pain when the user changes...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 2:47 pm
sdgray01 (8/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2011 at 2:41 pm
Viewing 15 posts - 32,956 through 32,970 (of 59,099 total)