Viewing 15 posts - 47,521 through 47,535 (of 59,099 total)
If you'd always like it to return Jan - Mar of the CURRENT year, then you don't even need to know what the current year is...
SELECT ID
...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 7:57 pm
evaleah (10/29/2008)
I deployed it to SQL 2005 and it appears in the Assembly area. The routine creates an iCalendar formatted email message and then sends...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 7:44 pm
Why? Try this and see why I ask... ask yourself "What is 1 divided by 3 times 3?" 😛
DECLARE @A DECIMAL(3,0), @b-2 DECIMAL(18,0),@F FLOAT
SET @A = 3
SET...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 7:30 pm
Is the "autoshrink" option turned on on TempDB??? If so, it must be turned off!.
Also, you need to figure out what the largest it will grow to, add 20 or...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 7:23 pm
Better than that, tell us what the CLR is supposed to do so we can try to show you how to do it without a CLR... there's usually a way......
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 7:15 pm
Heh... try this...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 7:12 pm
Heh... I've been doing SQL for almost 13 years... at least he used books... I still write the answers on my shirt sleeve. 😛
Nah... seriously... breaking out the books...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 7:09 pm
Don't ever turn autoshrink on for TempDB... talk about fragmentation!
Check the log file (LDF) for TempDB... is that what's actually full?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 6:54 pm
That is, of course, if you don't have the time in a separate column... let us know.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 6:51 pm
If it's trully a DateTime column, then MAX will flush out the one with the latest time "auto-magically".
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 6:50 pm
RML51 (10/29/2008)
I'm arguing with one of our VisualStudio/.NET developers about column order in tables. He's asking us to move columns around so they appear where he wants to see...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 6:37 pm
Damn! That's two times I missed the intended humor... ok... I'm going to my room to suck my thumb and twiddle my hair. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 6:23 pm
AnzioBake (10/29/2008)
My Solution returned 670000+ Rows...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 6:31 am
AnzioBake (10/29/2008)
To Test your Solution, I ran mine again as I made some changes. Execution time was 5 min 36 sec
I added a print statement after ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 6:02 am
Just a comment... my experience has been that even monster batch systems don't need parallelism in most cases if the code is well written and the correct indexes are in...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2008 at 5:57 am
Viewing 15 posts - 47,521 through 47,535 (of 59,099 total)