Viewing 15 posts - 18,481 through 18,495 (of 22,226 total)
Either bulk insert or some method of INSERT... SELECT... You can see examples in the Books Online.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 6, 2009 at 6:26 am
I wouldn't recommend doing this on a production system, but you could capture statement completion events from a trace. Then you'll see when the call is made from proc b.
However,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 6, 2009 at 6:25 am
Yeah, I saw the app. I do understand what you're describing, but I'm 100% with Gail on this. You need to gather statistics to understand exactly where the slow-downs are...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 6, 2009 at 5:34 am
Where you see proc, substitute query. Sorry I mistyped.
And yes, you do need to determine where the slow down is occuring because it's not from compile time on such simple...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 5:25 pm
DBCC DROPCLEANBUFFERS should only get run as a test. That removes all the data from memory. Based on the queries you've shown, compiles aren't your issue. You're looking at memory...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 5:05 pm
dacto77 (2/5/2009)
The output of my store has 2 tables, how can I insert these 2 tables into another 2 temp tables to manipulate the data? I use this store...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 1:12 pm
SCOPE_IDENTITY will work, but only if you ever insert a single row. If you insert two or more rows, SCOPE_IDENTITY won't adequately cover the situation. That's what the OUTPUT clause...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 12:59 pm
In addition to simply observing performance degrade, have you collected information from performance monitor to see if buffer cache hit ratio (just for one example) is maintaining over time or...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 10:36 am
That is scary. However, I wouldn't worry too much (worry some, yeah).
I'm hesitant to suggest what to do since this is PeopleSoft, but let's assume for a moment that it's...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 10:22 am
Possibly. But I think there might be some samples for how to do it locally.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 10:14 am
Run the query with an explicit open transaction statement:
BEGIN TRANS
...
Don't put in a commit until you're complete with your testing.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 10:11 am
To give you a complete answer, you'd need to post the code, deadlock graphs, database structures, etc.
To make a few suggestions, Does the table have any other clustered index? If...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 7:42 am
Mahesh Bote (2/5/2009)
[font="Verdana"]Grant Fritchey (2/5/2009)
The last post is close...Grant i didn't get you.
Mahesh
[/font]
Your post is close to the answer. The thing is, SCOPE_IDENTITY will only work for a single row...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 7:34 am
Lynn Pettis (2/5/2009)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 7:00 am
psangeetha (2/5/2009)
My criteria is when the parent rows are deleted, I dont want...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2009 at 6:09 am
Viewing 15 posts - 18,481 through 18,495 (of 22,226 total)