Viewing 15 posts - 6,346 through 6,360 (of 22,226 total)
SQLRNNR (4/13/2015)
Grant Fritchey (4/13/2015)
SQLRNNR (4/13/2015)
Grant Fritchey (4/13/2015)
SQLRNNR (4/13/2015)
Grant Fritchey (4/11/2015)
"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 13, 2015 at 12:06 pm
Brandie Tarvin (4/13/2015)
edyeh (4/13/2015)
"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 13, 2015 at 12:05 pm
Especially when doing an ONLINE rebuild, it's a combination of the transaction you're running to rebuild the indexes (might want to break that down to smaller transactions) combined with the...
"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 13, 2015 at 12:03 pm
Yes. A query hash is based on the query itself. So:
DBCC CHECKDB('Myfirstdatabase')
Is going to have a different hash value than:
DBCC CHECKDB('ADifferentDatabaseEntirely')
No shocks there at all.
"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 13, 2015 at 10:51 am
SQLRNNR (4/13/2015)
Grant Fritchey (4/13/2015)
SQLRNNR (4/13/2015)
Grant Fritchey (4/11/2015)
"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 13, 2015 at 10:48 am
The biggest part of the undertaking won't be making the calls to the objects. The biggest part of the work is all the modifications you'll have to make to all...
"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 13, 2015 at 9:34 am
I'm with Gail.
Although, if you wanted to you could make this a derived table and then GROUP BY the function. But I don't think it will help your performance any....
"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 13, 2015 at 9:32 am
If you're getting lots of inserts there's a good chance that during the day a healthy chunk of the information added to the table are falling outside of the statistics....
"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 13, 2015 at 9:24 am
The biggest question is are you using Enterprise functionality? If so, going to Standard, regardless of version is going to be an issue.
"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 13, 2015 at 9:08 am
You're making a modification to your server. Regardless of how "safe" that modification might be, yes, I'd make darn sure I have backups in place and that I've tested those...
"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 13, 2015 at 8:59 am
Sree Divya (4/13/2015)
thankscan any one tell differences between clustering and always on
Always On is a marketing term.
The two different services are failover clustering and availability groups. Failover clustering is...
"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 13, 2015 at 8:57 am
SQLRNNR (4/13/2015)
Grant Fritchey (4/11/2015)
"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 13, 2015 at 8:54 am
Yeah, it absolutely sends confirmation messages back. I wouldn't imagine that those, under most circumstances, are going to cause huge performance issues, but they absolutely do happen.
"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 13, 2015 at 8:53 am
Looks like a blog recommendation. Not a big deal to post those on SQL Server Central, but instead of putting it into the general forums which are usually reserved for...
"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 13, 2015 at 7:10 am
Looks like the exact same question over at ASKSSC. I gave very similar advice there.
If ever you wondered why so much emphasis is placed on backups, testing backups, ensuring backups...
"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 13, 2015 at 7:06 am
Viewing 15 posts - 6,346 through 6,360 (of 22,226 total)