Viewing 15 posts - 9,106 through 9,120 (of 22,224 total)
Sure. You can use SQL Agent to call the command line utility of Data Compare. You can then have that output to a report, generate a script or even update...
"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
January 10, 2014 at 3:53 am
ChrisM@Work (1/10/2014)
Grant Fritchey (1/10/2014)
Jeff Moden (1/8/2014)
rodjkidd (1/8/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
January 10, 2014 at 2:56 am
Jeff Moden (1/8/2014)
rodjkidd (1/8/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
January 10, 2014 at 2:35 am
Just a data insert alone will not affect plan cache (it sure can affect the rest of the cache). But, the update in statistics can affect recompiles. Maybe that's what...
"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
January 8, 2014 at 4:25 am
You can't really fragment an index with modifying the data. Don't test stuff in production.
"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
January 8, 2014 at 2:05 am
Sounds like a limit imposed by the operating system then.
"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
January 8, 2014 at 2:04 am
Hmmm...
I would suspect the statistics are going out of date and leading to a bad plan which is locking everything up, but that's a guess. There's not quite enough information...
"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
January 8, 2014 at 2:03 am
Are you on the latest service pack and cumulative update? I still don't have time to really dig into this, but thinking about the missing statistics, I'm wondering if you're...
"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
January 8, 2014 at 1:49 am
I'm overseas currently. I'm going to have to get back to you on the details here.
"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
January 7, 2014 at 11:00 am
What David said is accurate. The entire cost for the plan is stored in the first operator, SELECT/UPDATE/DELETE/INSERT.
"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
January 7, 2014 at 10:58 am
chandan_jha18 (1/7/2014)
Grant Fritchey (1/7/2014)
chandan_jha18 (1/7/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
January 7, 2014 at 6:59 am
Without resorting to a third party software, you can't. The only way to access a backup is to restore 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
January 7, 2014 at 6:03 am
So, you're not getting table scans, but the performance is still really bad? It may just be your process then.
Also, even though it's Express, you can use extended events 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
January 7, 2014 at 6:02 am
chandan_jha18 (1/7/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
January 7, 2014 at 5:57 am
Thinking about it some more, it's also possible you need space in tempdb.
"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
January 7, 2014 at 2:22 am
Viewing 15 posts - 9,106 through 9,120 (of 22,224 total)