Viewing 15 posts - 55,531 through 55,545 (of 59,098 total)
Crud... more spam, Rog. Will you cut it out, please? Do an article or get someone to review your product... and, it's not going to be me 'cause I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2007 at 3:59 am
Mal D!
Glad to see your posts... thought I was the only wirehead with the idea of "Yes, perhaps its time to re-evaluate", but in the direction of maybe it's worth...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2007 at 3:53 am
Thank you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2007 at 10:02 pm
Thanks for the feedback, Rom.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2007 at 4:14 pm
Thanks. It would be nice if you shared your solution with us... both the function and the cursor, please. ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2007 at 1:57 pm
First and foremost, Serqiy is correct... delimited data should not be allowed to be stored in the database. The inserts to the database should be done via a staging table,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2007 at 1:08 pm
That's why you shouldn't format in the backend... ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2007 at 10:14 am
Okidoki ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 5:47 pm
Boy, I'll say... dunno why I made the dupe check separate...
must've been that old donut I ate this morning ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 5:44 pm
Wonder why Seric thought that technique required knowing what the words are? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 5:29 pm
It's ok... that's why all the smiley faces...
you're doing the right thing... when you have a front end involved, let it do...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 5:26 pm
Heh... the reason why you didn't find it in Books Online is because formatting dates for a GUI in SQL is a really bad idea for about a thousand reasons,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 2:32 pm
Ok... let's say that's correct for a minute... what does something like the following cost in the short term? Nothing... schedule met... everyone was happy...
What's it costing them now? Somebody was...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 10:15 am
Well kinda...
Change the FK's to "CASCADE ON DELETE" and then you only need to delete from one table ![]()
Lookup "cascading referential integrity constraints" in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 10:11 am
P.S. If you do decide to go the temp table route as I suggested, then adding the appropriate indexes and a primary key on the temp table may help speed things...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 4, 2007 at 10:06 am
Viewing 15 posts - 55,531 through 55,545 (of 59,098 total)