Viewing 15 posts - 8,821 through 8,835 (of 22,226 total)
pmadhavapeddi22 (2/27/2014)
I would like to gain performance also 🙁Thanks for the reply
You have to then look at the query plan to determine where things are slowing down and how 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
February 27, 2014 at 8:18 am
A much, much, less accurate mechanism would be to capture the information from sys.dm_exec_query_stats. You can see the last executed date there. That will show you what has been called...
"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 27, 2014 at 8:13 am
sqldriver (2/27/2014)
Grant Fritchey (2/27/2014)
Best practice is, 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
February 27, 2014 at 8:06 am
I've never found Intellisense to work adequately. Another tool to try is SQL Prompt[/url] from Red Gate Software.
"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 27, 2014 at 6:28 am
Just remember that any of the conversions can prevent the use of statistics which makes the possibilities of scans on the data much higher.
Best practice is, like to like comparisons...
"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 27, 2014 at 6:25 am
Just remember that enforcing referential constraints doesn't just ensure good, clean data. You also get performance enhancements when the query optimizer knows that foreign key constraints are in place and...
"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 27, 2014 at 6:23 am
You've pretty much outlined what SSIS was built for. But, there's no automatic way to do it. You'll have to build the processes by hand.
"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 27, 2014 at 6:18 am
It sounds like blocking and resource contention. You'd need to monitor the server to see which queries are the ones that are being slowed down and then determine what resources...
"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 27, 2014 at 6:17 am
I'd suggest using a T-SQL script to restore from. Whatever mechanism is changing the backups nightly is surely discernable, and therefore repeatable. You can then just run the restore. There...
"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 27, 2014 at 6:15 am
quackhandle1975 (2/26/2014)
Grant Fritchey (2/25/2014)
"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 26, 2014 at 7:58 am
P Jones (2/26/2014)
"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 26, 2014 at 4:26 am
The only part of that statement I would disagree with is outputting trace data to a table. I wouldn't recommend that. I would output it to a file (or more...
"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 26, 2014 at 4:24 am
What Gail says.
But, just a little bit of help without the details.
All those != commands are going to prevent good cardinality estimates from the optimizer which is likely to lead...
"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 26, 2014 at 4:19 am
That value is for CLR procedures, not T-SQL procedures, per the documentation on sys.parameters. You can only pull out the defaults looking at the actual definitions of the procedures.
"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 26, 2014 at 4:14 am
Yep, that one gets us all at one point or another.
"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 25, 2014 at 3:23 pm
Viewing 15 posts - 8,821 through 8,835 (of 22,226 total)