Viewing 15 posts - 50,086 through 50,100 (of 59,091 total)
catriona_brown (6/11/2008)
How can I retrieve the date of the last Sunday of every month?
All these wonder formula's for calculating the last sunday of a month and I'm not sure we...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 5:44 pm
Blinking is good... keeps the bloodshot eyes in shape 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 3:55 pm
Lynn Pettis (6/12/2008)
Which track is right, the coding of the delete (I offered 2 solutions) or the fragmentation (disk and data)?
I was talking about the DELETE code... but, yes, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:54 pm
catriona_brown (6/12/2008)
I figured it out. An no still not an exam question.
Heh... ok, your turn... let's see it... 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:46 pm
Jeff Moden (6/12/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:43 pm
Matt Miller (6/12/2008)
--test data
declare @date datetime
set @date='01/01/2008';
select top 500 @date+n as date
into #tblDate
from tally
where n<501
--last sunday of the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:42 pm
You're right... I missed where the OP said that. Thanks, Christopher. And, yes... lookup Cross Tab Reports...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:28 pm
Ummm... there's some responsibility required on the part of the user... you make them enter it twice and not allowed to proceed unless they match. If they get it...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:26 pm
Heh... we don't have the accent 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:21 pm
That's a common mistake that many developers make... they comment something like that out so they can test and do a rollback... but they forget to put things back the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:19 pm
Lynn Pettis (6/12/2008)
Jeff Moden (6/12/2008)
The real fact of the matter is...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:14 pm
Good question... I've never seen that behavior before... Of course, it's been several revisions of SQL Server since I've actually had to write any GUI code.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 2:08 pm
Not sure the use of a correlated subquery (a form of hidden RBAR) will speed anything up here... Maybe...
The real fact of the matter is the OP says it...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 8:37 am
bobjbain (6/12/2008)
must be talking to myself on this thread!!
Would you rather have someone say something like... "I've never had such a requirement, never heard of such a problem, and therefor,...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 8:32 am
I agree mostly... the second one... just loose the square brackets for readability purposes and don't use aliases that require them with the rare exception being reporting queries.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2008 at 8:23 am
Viewing 15 posts - 50,086 through 50,100 (of 59,091 total)