Viewing 15 posts - 41,491 through 41,505 (of 59,067 total)
talltop-969015 (10/17/2009)
Still, no excuse to not do some research before posting....
Agreed... but sometimes folks don't even know what to look for especially when they're new to SQL. Some haven't...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 11:24 am
Thanks Allister. The reformatting is taking longer than any of us anticipated and I also have a late breaking bit of information that I'm adding.
For the code windows, you'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 9:56 am
jcrawf02 (10/16/2009)
Steve Jones - Editor (10/16/2009)
whoop upside?what's next, shocking keyboards? loud raspberries when someone responds?
Seconded, all in favor?:-D
Belt fed pork chop launcher sounds like more fun. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 12:59 am
Grant Fritchey (10/15/2009)
Jack Corbett (10/15/2009)
Okay threadiatics, if you have choice between putting data for multiple applications in 1 database because there is some common data or application specific databases?
Unless...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 12:53 am
Ummm... ok... take any split function that works on an VARCHAR(8000) and test it for performance using something less than 8k to split (sorry for being obvious). Then, just...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 12:35 am
zukko (10/8/2009)
sorry forgot to add the full script 😛
Thanks zukko.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 12:30 am
I was in a hurry so I didn't read Mark's post. He basically said the same thing that I did before I did.
Here's the code you posted...
select distinct a.empid
from...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 12:21 am
Paul White (10/16/2009)
Oh well, never...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 12:09 am
sonphan11 (10/16/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2009 at 12:00 am
s ss (10/16/2009)
Thank you so much Jeff. You put it way better than what I wanted to say in "The Thread".God bless you!
Regards,
Supriya
Thanks Supriya... this one bugged me. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2009 at 8:31 pm
Bob Hovious 24601 (10/16/2009)
I have a couple of questions:
(1) Who are you, and (2) what have you done with Jeff Moden?
Alternatively:
(1) What kind of tranquilizers are you...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2009 at 7:48 pm
First, because it's such an unusual requirement, I guess I'd like to know the business reason behind this, if you don't mind. Thanks.
Second, I have a question. What...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2009 at 7:23 pm
Heh... OK... cuffs don't match collar here...
In your original post, you say you have a view and you posted...
ALTER view [dbo].[[font="Arial Black"]vwLawsonGLAmounts_Memo[/font]] WITH SCHEMABINDING as....
... Then you go on to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2009 at 7:09 pm
GardenLady,
In the GLUnits table, what is the purpose of the DB_Units_13 column? What does it contain and why is it different for the following rows in the sample data?
Company...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2009 at 5:45 pm
By the way, GardenLady... Nice job on the data load for #GLUnits... it loaded without error. Not sure I can help the view, but I'm looking at it.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 16, 2009 at 5:24 pm
Viewing 15 posts - 41,491 through 41,505 (of 59,067 total)