Tag Info

Hot answers tagged

5

It's a bug. This Connect ticket has a workaround for it from Kendra Little: I was able to work around this issue by temporarily adding a scheduled to the Utility Information collection (@collection_set_id=4) with the SQL command below. After doing this I was able to complete the data collection configuration via the GUI successfully. Afterwards I ...


2

In your question, there is not enough information to see where the problem is from technical point of view; however, I can see that there is a problem in communication between you as developer and the DBA. This is not abnormal though as DBAs and devs do not always 'speak the same language'. Let's go the some points in your question: You should rely on the ...


2

Based on your comment about the "unwieldy" SP I'd almost guarantee that is at least part of your problem. Try running the following query replacing DBName and SPName as appropriate. USE DBName GO SELECT SUBSTRING(text, statement_start_offset/2, CASE WHEN statement_end_offset = -1 THEN 999999 ELSE ...


1

Starting with the highest and moving down: SOS_SCHEDULER_YIELD This wait type is usually caused when you have queries performing huge scans. I'd suggest checking to make sure you have the proper indexes in place and you don't have any out-of-date statistics resulting in an inefficient query plan. OLEDB OLEDB waits indicate that your query has to reach ...


1

Search for mysql-related packages that are now installed: rpm -qa | grep -i mysql Delete any packages like mysql, mysql-server, mysql-client, mysql-shared, mysql-shared-compat, mysql-libs. yum remove mysql-server You do not need to remove mysql library bindings like python-mysqldb, php-mysql, etc., unless they had a dependency with some of the previous ...


1

They just released new server & driver packages (7/25/2014). I had the same issue with the old drivers but with the 7/25 release it is gone.


1

So there's a couple of ways that this can happen. The queries in the blocking database reference objects within the blocked database. The queries are waiting for tempdb to allocate pages and one query is blocking another query. There is memory pressure and queries are waiting for memory to be allocated so they have to wait their turn in the memory ...



Only top voted, non community-wiki answers of a minimum length are eligible