Viewing 10 posts - 1 through 10 (of 10 total)
opc.three (5/26/2011)
john jin (5/26/2011)
Similar things happened to us. It helped a lot after we did configuration changes as you said.Why not have a try?
Sorry, but this is an irresponsible comment...
May 26, 2011 at 8:30 pm
Would you mind to show the stored procedure and
rows of those tables involved in this stored proc
May 26, 2011 at 6:21 pm
What can you do?
CPU / Memory / DB size / Table size / Query plan / Trace ....
Please post these key information
May 26, 2011 at 6:08 pm
Unless you have many source to delete tableA, I think the best way is to change the "delete" program.
For example, you have a procedure [pro_delete]to delete tableA,
in this proc, when...
May 26, 2011 at 4:56 pm
Similar things happened to us. It helped a lot after we did configuration changes as you said.
Why not have a try?
May 26, 2011 at 4:41 pm
How about calculate the summary first (to the payment table), then inner join to the ticket table?
I am not sure about this.
I think by this design it's a little bit...
May 22, 2011 at 5:11 pm
It's interesting, I don't have a solution for you, but when you insert something you actually don't need to write so many insert statements
You can just write one statement
insert into...
May 19, 2011 at 8:24 pm
Index of the the table of SAM_Keywords
May be not good.
November 12, 2009 at 9:41 pm
It's very funy to run 32-bit system with 32G RAM
November 5, 2009 at 2:47 pm
By right even you delete 800,000 records shouldn't cause problems.
It's not about 2G or 4G memory in your machine,
Can you please post that query?
November 2, 2009 at 11:08 pm
Viewing 10 posts - 1 through 10 (of 10 total)