Viewing 15 posts - 5,611 through 5,625 (of 7,614 total)
In theory, the code below would do what you've described.
select t2.*
from Table2 t2
where
exists(select 1 from table1 t1 where t2.detail like '%' + t1.ID +...
November 25, 2014 at 9:47 am
ZZartin (11/21/2014)
g.britton (11/21/2014)
ScottPletcher (11/21/2014)
You don't "have" to do the FETCH twice. In fact, I never do that, because it's too error prone when the code is changed.
good point, though...
November 21, 2014 at 3:45 pm
g.britton (11/21/2014)
ScottPletcher (11/21/2014)
You don't "have" to do the FETCH twice. In fact, I never do that, because it's too error prone when the code is changed.
good point, though the...
November 21, 2014 at 3:02 pm
I use a different approach.
I have a nonbusiness dates control table where one first defines the general and specific nonbusiness dates wanted. Then you call a stored proc with...
November 21, 2014 at 2:43 pm
You don't "have" to do the FETCH twice. In fact, I never do that, because it's too error prone when the code is changed.
November 21, 2014 at 2:38 pm
He already has a partial design in place, I suspect his previous Developer left him with a few ideas, now he's asking if I can help him through.
First, start over...
November 21, 2014 at 1:20 pm
Jeff Moden (11/20/2014)
ZZartin (11/20/2014)
November 20, 2014 at 3:37 pm
No, DBAs should not know and definitely not store end user passwords, period.
App passwords are a different matter, and it can depend on the app. But stored passwords should...
November 20, 2014 at 2:02 pm
You can't calculate "work hours" without "in" and "out" markers. The work time calc is very easy if you a matching "out" for every "in".
November 20, 2014 at 1:46 pm
In other words, you need to create a new table that explicitly specifies the clause:
CREATE TABLE ... (
...
TEXTIMAGE_ON [new_filegroup_name]
...
November 20, 2014 at 1:23 pm
It's almost certainly the NTEXT that is the bulk of the data, and you can't move it without recreating the table entirely. Btw, you should change the ntext to...
November 20, 2014 at 1:21 pm
No, that's true, but you could use it in a view.
November 20, 2014 at 10:53 am
I wasn't not sure what '20140601' was relative to the run date. Is it the current month, the next month, 6 months ago?
Therefore, I used @month_1 to hold the...
November 20, 2014 at 10:50 am
swhetsell (11/20/2014)
ScottPletcher (11/19/2014)
November 20, 2014 at 10:35 am
NULL will never be "LIKE" or "=" anything. To allow NULL values, you'd have to add:
WHERE (column_name LIKE '%' OR column_name IS NULL)
November 19, 2014 at 4:33 pm
Viewing 15 posts - 5,611 through 5,625 (of 7,614 total)