Viewing 15 posts - 53,131 through 53,145 (of 59,098 total)
Heh... deletes make me nervous, anyway... constitutes some form of lost data. I don't use cascade deletes because I want people to have to work at doing deletes. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 9:19 pm
If memory serves correctly, I believe that form of index hint is "deprecated". Try this, instead...
select ACCT_NUM, OPERATOR_NUM, BRANCH_NUM
from TRANS_J_DATA_FULL WITH (INDEX(IX_TRAN_FULL))
where TRANS_DATE >= @dStartDate and TRANS_DATE <= @dEndDate...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 9:16 pm
Don't use either... use the functions built for this...
1. Check if temp table exists...
IF OBJECT_ID('TempDB..#temptablename','U') IS NOT NULL
PRINT 'Table Exists'
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 8:38 pm
Heh... in other words, there's no such thing as a Julian date of "107999"... can only go up to 107365... next day would be 108001.
With that in mind, the following...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 8:13 pm
How did it help? What was the problem?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:59 pm
Never import directly to the final destination table... import into a staging table... should be able to use a default on a staging table but, if not, just update the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:57 pm
Two way street here... please share your solution.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:48 pm
Heh... do you intend to print that size sheet?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:44 pm
Test the code in the presence of the indexes and not... that's the only real way to tell.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:34 pm
That's one of the best compliments anyone could ask for, James. Thank you, Sir!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:16 pm
14k characters? What on earth are you doing?
Still, Exec will handle many more than 14K characters... so that's not the problem. Can't tell what's causing the problem 'cause...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:12 pm
Please share what you did...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:03 pm
Both will take the same time because EM7 will run the same code as what you've typed behind the scenes...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:57 am
Yes, thank you for the feedback and I agree that a clustered index will, in fact, make the concatenation run much faster... except that most folks aren't going to dedicate...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:55 am
So...are you saying I can have a procedure do what this functions does?
Well, kind of... before SQL Server 2000, there was no such thing as user defined functions... people ended...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 4, 2008 at 7:16 am
Viewing 15 posts - 53,131 through 53,145 (of 59,098 total)