Viewing 15 posts - 6,646 through 6,660 (of 22,219 total)
Personally, the single most important thing here is getting rid of the multi-statement table valued function. Those things are nothing but trouble.
After that, I think everyone else has offered lots...
"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, 2015 at 12:57 pm
Assuming the Threadizens are aware of this since you're a giant bunch of nerds, but...
Spock is dead.
Leonard Nimoy passed away today.
"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, 2015 at 10:38 am
Lynn Pettis (2/26/2015)
... Mark one off, 1 day on the calendar to go. 1 day on the calendar to go, 1 day to go, ...
Should have said something when I...
"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, 2015 at 10:37 am
Yeah, a derived table or a Common Table Expression would allow you to do that. Sorry I didn't understand what you were asking.
"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, 2015 at 8:09 am
There is no way.
Go to your last known good backup.
"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, 2015 at 6:34 am
You could try doing some of the work in 2014 using In-memory. It still logs things, but not in the same way, at all, especially if you use eventual consistency.
"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, 2015 at 6:33 am
Replacing just some of the spaces and not other spaces with no precise set of rules means the Mark I eyeball is going to have to be used to do...
"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, 2015 at 6:31 am
What situation are you seeing this in? I'm unclear as to whether we're inside SQL Server or in an application?
"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, 2015 at 6:29 am
I'd suggest taking a look at Minion Reindex. I wrote a review of it here[/url]. I think that'll help 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, 2015 at 6:28 am
john.ward 24608 (2/27/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
February 27, 2015 at 6:24 am
It also depends on how your filegroups are setup and how your objects are stored within the filegroup. It's entirely possible that you've got specific sets of data going to...
"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, 2015 at 6:19 am
My concern would be how the function is applied to arrive at the checksum. But I'm with everyone else, why not just let them hit the string. Also, I'd consider...
"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, 2015 at 6:18 am
Instead, I'd go with a more standard approach:
select name AS [Table Name],
create_date AS [Date created]
from sys.tables;
select @@spid...
"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, 2015 at 6:08 am
The only way I can think to do this would be to capture the query metrics for all the databases and then group the data. There's nothing that splits CPU...
"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, 2015 at 6:06 am
My preference would be to have pre-grown data files. I can control when it grows and how much it grows. This matters because auto-grow will cause blocking while the growth...
"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, 2015 at 6:05 am
Viewing 15 posts - 6,646 through 6,660 (of 22,219 total)