Viewing 15 posts - 6,661 through 6,675 (of 22,226 total)
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
Have a full deployment testing process that builds your test scripts and test databases from a source control system. That way you can ensure that what you're deploying works 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, 2015 at 6:02 am
ANn -425914 (2/26/2015)
For SQL performance tuning for a query, does the order of columns in where filter clause matters?
In most cases, no. But, that's because the optimizer will arrange 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, 2015 at 6:00 am
Nuts. Just spent 20 minutes looking through the books. Wonder if I hallucinated this book.
"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, 2015 at 1:07 pm
SQLBill (2/26/2015)
Sioban Krzywicki (2/26/2015)
Grant Fritchey (2/26/2015)
Brandie Tarvin (2/26/2015)
Jeff Moden (2/25/2015)
Brandie Tarvin (2/25/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 26, 2015 at 12:29 pm
Clearly clarity and computer science don't always go hand in hand.
I'm pretty sure using the query should get you ballpark close. It won't be perfect. I'm pretty sure the value...
"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, 2015 at 11:27 am
Wait, so that means it wasn't a column, but part of a result set?
"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, 2015 at 11:23 am
It's actually 1024, not 1000. That equates to 359kb. Probably what's not included is header information and meta-data about the backup itself. That would explain the extra 19kb.
"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, 2015 at 7:56 am
spaghettidba (2/26/2015)
Lowell (2/26/2015)
arrjay (2/26/2015)
The results don't include objects which have not been written/read to/from i.e. nulls. Is there a way of returning these stats? ...
"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, 2015 at 7:51 am
Viewing 15 posts - 6,661 through 6,675 (of 22,226 total)