Viewing 15 posts - 52,921 through 52,935 (of 59,091 total)
Clever... effective... and vengeful... all in the same action... I LIKE IT! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:15 am
Hi Mark,
Thanks for the feedback.
On the posting of XML you mentioned... The best thing to do would be to simply attach the XML as a file...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:11 am
Jeff Moden (1/14/2008)
Yes... use "Dynamic SQL" to accomplish this...
Ack... not enough coffee... sorry.
Gail's (GilaMonster) post is correct for this...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:09 am
Chirag (1/15/2008)
between '2008/01/01 12:00:00:000 AM' and '2008/01/01 11:59:59:997 PM' if u want all records between the 2 dates.
Just a suggestion...
The optimizer is going to evaluate the BETWEEN code in...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2008 at 5:03 am
Heh... I take the low road... disable all logins (except mine), answer the phone to see who's squawkin' 😉 (just kidding... in most cases 😛 )
Great article, David!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 9:47 pm
suma (1/14/2008)
i tryed sys.all_object, sys.procedures but no luck.
Sorry, didn't see that... if you can't find it there, then I don't know where it might be, especially if you're logged in...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 9:35 pm
Yes... use "Dynamic SQL" to accomplish this...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:30 pm
Heh... "get out there and strike a blow for liberty."
... and we'll leave the lights on for ya!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 14, 2008 at 5:18 pm
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
Viewing 15 posts - 52,921 through 52,935 (of 59,091 total)