Viewing 15 posts - 8,296 through 8,310 (of 22,214 total)
You've conflated rows with pages. The number of rows doesn't really matter. It's the number of pages that affects how index defragmentation occurs within the index. If the index is...
April 30, 2014 at 5:08 am
Pretty sure Koen has nailed it already. The JOIN is likely to change the order in which data is retrieved, so a sort operation will be necessary.
April 30, 2014 at 5:04 am
It sounds like you're hitting bad parameter sniffing. But, without seeing the "good" and "bad" execution plans, it's hard to know for sure. You need to capture both plans and...
April 30, 2014 at 5:02 am
mister.magoo (4/29/2014)
Grant Fritchey (4/29/2014)
Try using the WAITFOR command in T-SQL. That'll pause the execution of the query and you should see a timeout.
Except that will be a Command Timeout, not...
April 30, 2014 at 2:49 am
Assuming you don't have throttling enabled and just have the default group, you can get it from here:
SELECT * FROM sys.dm_os_performance_counters AS dopc
WHERE dopc.counter_name = 'cpu usage %'
AND dopc.instance_name =...
April 30, 2014 at 2:36 am
According to the statistics you're moving 197 million rows with no where clause. Don't bother with an index. It won't do any good. As currently built out, there's almost nothing...
April 30, 2014 at 2:30 am
Yeah, but that's index fragmentation. Shrinking and growing a database file fragments at the OS level. There's a decent little article about how to look at this over here at...
April 29, 2014 at 3:47 pm
TheSQLGuru (4/29/2014)
April 29, 2014 at 3:42 pm
Try using the WAITFOR command in T-SQL. That'll pause the execution of the query and you should see a timeout.
April 29, 2014 at 3:38 pm
You can get the plan_handle by querying sys.dm_exec_query_stats or sys.dm_exec_proc_stats if it's a stored procedure. If you need to use sys.dm_exec_query_stats, you can combine it with sys.dm_exec_sql_text in order to...
April 29, 2014 at 3:37 pm
New Born DBA (4/29/2014)
And I also mentioned that we are shrinking the DB every week, so you guys don't think that's what's causing the problem right?
I'm not saying this...
April 29, 2014 at 3:21 pm
The query times aren't terribly long at 200-800 milliseconds or so. But the fact that you're using sp_trace_getdata to collect information means you gathered this using the GUI. Don't do...
April 29, 2014 at 11:54 am
I only go to the clouds for my demos if I'm actually demoing cloud stuff. Too much can go wrong in demos anyway. Adding in connectivity on top of it...
April 29, 2014 at 11:46 am
scott_lotus (4/29/2014)
The "WAIT STATISICS" tab is currently showing 75% MISC WAITS.
I will check it again during the index creation and publish...
April 29, 2014 at 11:34 am
Just in terms of management, loads and loads of databases is a bit of a nightmare. But, from the standpoint of separation of customers, it's not a bad idea. Also,...
April 29, 2014 at 11:30 am
Viewing 15 posts - 8,296 through 8,310 (of 22,214 total)