Viewing 15 posts - 58,711 through 58,725 (of 59,091 total)
Wasn't that lucky... it's 24/7. We get to bounce the server once a week for "impacting changes" for about 30 minutes... then, QA get's to verify what we've done. Of...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 23, 2005 at 9:36 pm
Yeah, I wish I didn't need it! Wonderful 3rd party solution at work. Bunch o' DB rookies... these are the same wonderful folks that built an Oracle-Like sequence table (NextID)...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 23, 2005 at 7:47 pm
Hang on there, Paully21, I'll get to you in a minute...
I absolutely agree with everyone that having CSV columns in a table is a basic form of "death by SQL". ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 22, 2005 at 8:29 pm
LMBO! Both at the design and your great sense of humor which allows you to calmly handle the mess they've heaped upon you! I don't know about anyone else, but your...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 22, 2005 at 8:19 pm
Dang! I must be old! None of the newer online slang dictionaries has SOFH or BSOFH! Remi, where did you find that definition?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 22, 2005 at 5:28 pm
Ok, ok... you got me... I've got dirt in my garden that's younger than I am...
As you can tell, though, I've had...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 22, 2005 at 4:58 pm
Remi is correct... it takes the original description and wraps it in single spaces. Basically, it allows this single search ('% myword %') to work on the following descriptions...
something myword...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 22, 2005 at 4:45 pm
Ok... but the scenario you just stated exactly fits the methods I suggested... whatever.
To answer your original question, you need to use some Dynamic SQL to do what you want......
--Jeff Moden
Change is inevitable... Change for the better is not.
August 22, 2005 at 5:43 am
Here's a way to avoid the table scan...
select * from task where Descr LIKE '% myword %' OR Descr LIKE 'myword %' OR Descr LIKE '% myword'+char(10)+'%'
If you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 22, 2005 at 12:01 am
IMHO, archiving data into separate monthly named databases is one of the worst things you could do... they (3rd party provider) did the same thing were I work and it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 21, 2005 at 11:48 pm
Does this do it for ya?
SELECT 'ID1' AS IDName, ID1 AS IDValue FROM yourtable
UNION ALL
SELECT 'ID2' AS IDName, ID2 AS IDValue FROM yourtable
UNION ALL
SELECT 'ID3' AS IDName, ID3...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2005 at 11:56 am
I know what you mean... It's only when they live up to the name of "BSOFH" and they've got that control thing going on... or, they're just plain old stupid.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 20, 2005 at 11:27 am
I gotta agree with THAT! Between a tally table (you guys call it a numbers table) and/or a date table (mine are combined into one which is why I called...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2005 at 9:35 pm
Cool... Thanks Noeld. It's been so long since I've used a trusted connection, I almost forgot they existed. ![]()
I'll probably keep using linked servers, though,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2005 at 10:58 pm
One of the things I don't like about open row sets is the login information is in the query... and, no, I prefer not to encrypt queries especially on development...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 17, 2005 at 7:00 am
Viewing 15 posts - 58,711 through 58,725 (of 59,091 total)