Viewing 15 posts - 52,936 through 52,950 (of 59,098 total)
I'll just bet the phantom proc is stored in the Master database 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:59 pm
You'll get a "Divide by Zero" error if the following ever resolves to zero... plan on it...
(Sum(CASE WHEN ISNULL([MailDate1], 0) = 0 THEN 0 ELSE 1 END))
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:57 pm
Ok... let's try this one more time and then I'm just going to ignore your posts in the future...
Read this, do this, or forget this...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:52 pm
Heh... Keep in mind that the BETWEEN examples are rarely correct because they don't allow all times of the day to be included or they mistakenly include dates with...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:49 pm
SQL33 (1/14/2008)
Me too, unfortunately, that's not an available option.Thanks!
Heh... it's always an option if the nail in the bat is large enough and you can find the designers that put...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:47 pm
Dumb question... are you trying to test the code while the spreadsheet is open? If so, BOOOM! You'll get the error you got.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:44 pm
What's are the common columns between the two tables? Gotta have something to join on to start with.
Recommend you post the schema for both tables...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:29 pm
Perfect... thanks for taking the time to post your feedback!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:16 pm
Thanks for the feedback, Chris... glad it helped.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:07 pm
The Nirvana that you hint about. This is only likely to exist when all IT systems are in a constant state of renewel, and there is no legacy to deal...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 4:02 pm
Heh... worse... RBAR on steriods over the "pipe".
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:57 am
Heh... lemme say it again...
The user that the SQL Service logs in as, must have permission to "see" the share.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:54 am
Heh... thanks... good to know.
And, my bad... didn't look at the first post... this is Oracle code...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:49 am
Because in a proper mixed format fixed field data set, each row will have a "rowtype" marker. Mixing header information in the data will frequently cause bulk loads to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:46 am
Sure, Praveen... I just said that 😉 but thanks for the feedback.
And, my bad... Ramesh was the one that said it needed to be done without a temp table and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:34 am
Viewing 15 posts - 52,936 through 52,950 (of 59,098 total)