Viewing 15 posts - 8,146 through 8,160 (of 22,224 total)
The big one for me would be that you can just add a nonclustered columnstore index to the table, but still have the table stored as a regular SQL Server...
"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
May 14, 2014 at 3:29 pm
First thing I'd suggest is not trying to do this with stats. It's fine when collecting information for one query. As soon as you start collecting two, three, etc., 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
May 14, 2014 at 3:20 pm
Why are you using common table expressions here? You define this:
WITH results
AS (SELECT id,
...
"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
May 14, 2014 at 12:47 pm
How are you measuring the time? From the SSMS client? That includes the time to transmit across the wires and isn't a good measure of server performance. If you really...
"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
May 14, 2014 at 12:27 pm
I'm assuming you're getting the fragmentation information from sys.dm_db_index_physical_stats. If so, are you using the DETAILED mode to gather your metrics? I've never seen SAMPLED or LIMITED take very much...
"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
May 14, 2014 at 10:50 am
The only way to get a really accurate count would be to use extended events or trace. Since you're 2008 trace will be easier since there is no GUI 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
May 14, 2014 at 10:48 am
That's a client testing issue. You're not going to see any problems from it during your upgrade in SQL Server, side-by-side or in-place. But you could see issues on 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
May 14, 2014 at 8:51 am
It's absolutely using sys.dm_os_waits_stats. But if you want to know which query, just run extended events/trace to capture 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
May 14, 2014 at 8:07 am
SQLRNNR (5/14/2014)
Grant Fritchey (5/14/2014)
Ed Wagner (5/14/2014)
Koen Verbeeck (5/14/2014)
GilaMonster (5/14/2014)
Koen Verbeeck (5/14/2014)
This was a funny topic 😀 (especially the last replies)Sorry, am a little short on patience today.
I pretty much laughed...
"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
May 14, 2014 at 8:01 am
Again, if you do a search on the internet, there are tons of articles on this. Not just one. Here's a blog entry from MS on troubleshooting the issue. This...
"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
May 14, 2014 at 8:00 am
Greg Edwards-268690 (5/14/2014)
Grant Fritchey (5/14/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
May 14, 2014 at 6:26 am
I'd say show them that error message and let them look it up through Bingle. It's absolutely a hardware related problem and it's very well documented as such out on...
"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
May 14, 2014 at 6:20 am
Check the documentation on the BACKUP command. There is no facility for just getting the READ_ONLY file groups. You'll have to go after each one individually. Partial backup documentation says...
"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
May 14, 2014 at 6:13 am
Blocking caused by another process doing an INSERT/UPDATE/DELETE which will stop the scan.
"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
May 14, 2014 at 6:08 am
It's absolutely an I/O issue. I'd say your disks are being overwhelmed because the issue isn't that a given process is waiting for disk access while another process uses, but...
"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
May 14, 2014 at 6:07 am
Viewing 15 posts - 8,146 through 8,160 (of 22,224 total)