Viewing 15 posts - 6,256 through 6,270 (of 22,226 total)
Just call it right within the procedure as stated. Here's the documentation.
"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
April 27, 2015 at 3:13 am
Have you looked at the execution plan for the query? That will tell you why it's running slow.
"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
April 27, 2015 at 3:09 am
You can include this information in the connection strings from the application and then it will be available in SQL Server. But, if it's not a part of the connection...
"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
April 27, 2015 at 3:08 am
Service Broker is a messaging and queuing engine within SQL Server. You can read more about it in the Books Online. It appears that this error was addressed by a...
"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
April 27, 2015 at 3:04 am
In that case I'd just pull them directly from source and publish them that way. PowerShell will be fully automatable, you can connect to multiple servers, and with threading you...
"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
April 25, 2015 at 8:40 am
I'd suggest writing a PowerShell script to run the export and import of the procedures. That should be fully automated and ought to work well.
Another approach would be to put...
"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
April 25, 2015 at 8:31 am
I think your logic is sound. I'm just a big fan of testing things to be sure.
"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
April 24, 2015 at 12:35 pm
Stephanie Giovannini (4/24/2015)
Suppose my table looks like...
"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
April 24, 2015 at 10:33 am
Why 100K rows? Is it an export? If it's not an export of data, 100K is not a reasonable number of standard evaluations.
"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
April 24, 2015 at 10:21 am
Then you might be running into resource issues, not enough memory, possibly contention in tempdb, the log file was growing over and over? Something along those lines.
"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
April 24, 2015 at 7:08 am
You could set up a trigger to capture inserts. That might cause some performance hits though. You could capture queries using extended events and sort out the INSERT statements. It...
"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
April 24, 2015 at 6:34 am
200 million rows isn't really that big and that's a long time for an index to run. I suspect you may have been experiencing blocking. The thing to do would...
"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
April 24, 2015 at 6:30 am
For an insert query, those are the full results. You're seeing exactly what you should. You inserted a row. It was completed successfully. An insert doesn't return data.
"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
April 24, 2015 at 6:28 am
The thing to do might be to hire a consultant to do the job description and the interviews for you. As Jeff says, you've split the difference between a BI...
"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
April 24, 2015 at 6:22 am
I've seen a 5 minute compile time on queries, so they can run for a very long time indeed. If you're looking at the plan, you can see the compile...
"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
April 24, 2015 at 6:15 am
Viewing 15 posts - 6,256 through 6,270 (of 22,226 total)