Viewing 15 posts - 57,916 through 57,930 (of 59,099 total)
How true... fortunately, I have DBA's that do notice the difference
but it's good to check.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2006 at 4:16 am
Having a calendar table would certainly assure correctness. If you can do that, that would probably be the best way to go...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 7, 2006 at 4:12 am
Correct... SQL Server's UPDATE statement is one of the more useful ones in that it actually has TWO from clauses that are specifiable... most people leave out the first FROM...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2006 at 9:58 pm
UPDATE tb_comments
SET user_id =
(SELECT id_tb_comments, tb_users_crm.id_user
FROM tb_comments
INNER JOIN tb_jobs ON tb_comments.job_id = tb_jobs.id_tb_jobs
INNER JOIN tb_school ON tb_jobs.school = tb_school.id_tb_school
INNER JOIN tb_portfolio ON tb_school.folio_id = tb_portfolio.id_tb_portfolio
INNER JOIN tb_users_crm ON tb_portfolio.id_tb_portfolio =...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2006 at 8:01 pm
Ok... here we go... let's NOT do it on the BULK INSERT side... let's do it where you tried to insert into the daily feed file from the temp table...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2006 at 6:23 pm
That's why I did a test on 10 million records... your chunks will be easy.
Your temp table load is fine...
I've suggested it 3 times now, John... for the temp table...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2006 at 2:10 pm
SG,
Man, Serqiy is right and Celko would have fun this this one... Why are you splitting an attribute into separate tables? What is it that you are trying to do that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 6, 2006 at 8:28 am
Just on the outside chance you didn't know... you do realize that SQL Server must be installed on a Windows Server? (Except for the Developer's Edition, of course)?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 7:35 pm
Thanks for the tip, Serqiy... if I ever let my guys put text in the database, that'll help a lot.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 7:15 pm
| Thankd for your reply JEff, with regards to naming files daily, the problem is that w eneed to... |
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 7:11 pm
There are tons of possibilities including exclusive locks and deadlocks that will cause almost instant timeouts... The use of sp_Lock followed by the use of sp_Who2 for the offending SPID...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 11:14 am
Yep... I agree with that...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 11:06 am
I guess that doesn't even matter...
Whatever you use to uniquely identify a CDR with (1 column or multiple columns), here's what I'd do...
First, I just don't understand the need for...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 10:13 am
Yep, I understand what you are doing... I just don't know why...
sp_Recompile 'tablename' will (from Books Online) recompile the stored procedures and triggers that use the object to be recompiled the next...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 9:57 am
Crud, I asked the wrong question...
If the CDRFingerPrint is duplicated, does that give an indication that the same CDR is in the temp table more than once?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 5, 2006 at 9:18 am
Viewing 15 posts - 57,916 through 57,930 (of 59,099 total)