Viewing 15 posts - 50,641 through 50,655 (of 59,099 total)
You can if the in and out times are truly date times...
Please post some of the input data and the real table schema. Please see the URL in my...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 4:28 am
Deprecated... another word for "we're taking another feature away". I understand that deprecated aliasing by equality and forcing AS. Too bad... aliasing by equality made for some very...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 12, 2008 at 4:24 am
The real key is that the other folks are right... there should be a separate DB for each company. I've found that when the "higher ups" get involved, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 8:02 pm
Another question would be... if you're converting TEXT to VARCHAR(4000), why don't you just pass VARCHAR(4000)? In fact, why waste time... do the conversion without a UDF...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 7:58 pm
heh... looks like homework... you forgot to remove the extra brace character from the example you copied out of Books Online. 😉
Also, you say this worked and now it doesn't....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 7:55 pm
Actually, the method you've shown won't work either... the INTO is in the wrong place. 😉 As a sidebar, you really shouldn't use global temp tables... to much of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 7:51 pm
Oh, I absolutely agree! Seems like MS has been making a lot of changes to things, lately... most of them boil down to removing some "feature". Case sensitivety...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 12:34 pm
Actually, I don't think it was a "simple mistake"... I think it was a cost cutting measure. It doesn't take nearly the code to make something case sensitive at...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 12:07 pm
15 million rows per month isn't much. Instead of looking for a hardware solution to a software problem, the best thing to do would be to follow the suggestions...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 11:54 am
My first question would be, why do you have a join to the Location table when you're not selecting anything out of it? Are you just using that as...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 11:48 am
I've found Zero applications that actually require case sensitivity... If I ever do, I'll change the collation on the columns that do rather than setting the whole database for it....
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 10:51 am
Heh... you live on a "farm", Steve... you know what it means to "close the barn door after the cows got out."
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:53 am
Without knowing what the 7 tables are, I'd say that's the better choice than trying to store it all as XML both from a design/maintainability aspect and a performance aspect.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:52 am
Try this link... also, do a search on "SQL SERVER TUTORIAL" and "T-SQL TUTORIAL"...
http://answers.yahoo.com/question/index?qid=20080229151637AAfb5Gu
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:50 am
Thanks, Anirban!
I absolutely agree. Steve Jones recently wrote an article asking the quesiton "Why do you write"? One of the reasons I pointed out was the incredible amount...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 11, 2008 at 9:36 am
Viewing 15 posts - 50,641 through 50,655 (of 59,099 total)