Viewing 15 posts - 51,661 through 51,675 (of 59,091 total)
Lynn beat me to it... 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 4:30 pm
You're welcome... but the IMAGE datatype is 2 GB... the (16) is just a pointer... the following is from BOL 2000...
Image
Variable-length binary data from 0 through 231-1 (2,147,483,647) bytes.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 4:29 pm
If you print your SQL variable, you'll find that your @@FortnightEndDate variables are returning values that need quotes around them... it's an easy fix...
'and(t.trandate>='''+@@FortnightEndDate-13+'''and t.trandate=''' + @@FortnightEndDate +''')'
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 4:24 pm
Lynn Pettis (3/17/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 4:16 pm
Heh... the first indication of a problem would be the 1 or 2 hours that it originally took never mind the 6-8 it's taking now! 😉
You wrote...
The DTS queries...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 4:05 pm
Since it's a PDF file, maybe save it in an IMAGE datatype in 2000 instead?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 3:54 pm
Don't waste your time on that... answer a quick question instead...
Triggers fire on any update... If I update a name from 'Jeff' to 'Jeff' (not a type-o, they are the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 3:43 pm
Here's both an answer to your current dilema and what to watch out for in the process...
http://www.sqlservercentral.com/articles/Test+Data/61572/
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 3:38 pm
I think you may have a misunderstanding of what it does... VarDecimal has nothing to do with the MONEY datatype. The only time that VarDecimal saves space is if...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 3:23 pm
Did you look at the "Message" window? Sometimes one or the other runs in half the time as the other. Some folks look at something like that on...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 3:15 pm
Perfect... the next thing to do would be to practice a little of what we call "forum etiquette"... 😉 How did you solve it and would you mind posting...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 3:06 pm
Heh... No doubt... I can see the RBAR on steroids now... some of my favorite misuses are SPLIT/CONCATENATION functions in batch code, UDF's that format dates so they can be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 3:04 pm
And then you better make sure you run the code more than once, even on a quiet system...
DECLARE @Year INT
SET @Year = 2008
SET STATISTICS IO ON
SET...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 2:46 pm
LMAO!!! ROFL!!! Now that's funny stuff... I don't care who you are, ya gotta laugh at that! (Thanks for the quote Larry TCG). 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 2:33 pm
Chris Morris (3/18/2008)
Jeff, you like playing with macros in Excel
Heh... no I don't... I hate the darned things... That's why I like the second of my two methods the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2008 at 2:29 pm
Viewing 15 posts - 51,661 through 51,675 (of 59,091 total)