LOCK_ESCALATION = TABLE is the default behavior in SQL Server 2008 & is the ONLY behaviour in SQL Server 2005. You can safely drop the statement without any change in functionality.
I would suggest that you come at the problem from two perspectives. Trap or Catch Deadlock Errors so that you can re-run the transaction that is chosen as the Deadlock Victim by the SQL Server database engine. Find out what is causing your Deadlock Events. You can do this in one of two ways, either … Read more
Once I determined that it is the ADO.NET connection at the root of the problem, this thread led me to the answer. Basically connections through Sql Server Management Studio (SSMS) by default have SET ARITHABORT ON. ADO.NET connections do not. Setting ARITHABORT OFF and executing the query directly through SSMS gives me the same slow … Read more
See jTDS FAQ http://jtds.sourceforge.net/faq.html you will have to pass useNTLMv2=true and domain=yourdomain
You can’t set filter to trace specific table directly. What you can do is specify a filter for Text Data: File -> Properties -> Event Selection -> Column Filters -> TextData -> Like -> [Table Name] You may find it important to wrap your table’s name with wildcard characters: “%table name%”.
You’re probably looking forwith (updlock, holdlock). This will make a select grab an exclusive lock, which is required for updates, instead of a shared lock. The holdlock hint tells SQL Server to keep the lock until the transaction ends. FROM TABLE_ITEM with (updlock, holdlock)
You are missing the condition inside the sub query. SELECT t2.Id, STUFF((SELECT ‘,’ + CAST(VALUE AS varchar) FROM @MyTable t1 where t1.Id =t2.ID FOR XML PATH(”)), 1 ,1, ”) AS ValueList FROM @MyTable t2 GROUP BY t2.Id Demo
I found the answer here. It says In SQL Server 2005 and later, the SQL Server Profiler graphical user interface displays the Duration column in milliseconds by default, but when a trace is saved to either a file or a database table, the Duration column value is written in microseconds I was watching them after … Read more
I did some searching and was unable to find any keyboard shortcuts for executing individual lines in SSMS. There is a reference online though. http://msdn.microsoft.com/en-us/library/ms174205.aspx Personally I just highlight the row in question (Shift + End or Shift + ↓, etc.) and hit F5. Ctrl + E works just as well on a Mac.
You’d need COLLATE in both places most likely. Select City COLLATE DATABASE_DEFAULT AS Place, State, Country FROM DEPT1 UNION ALL Select ” COLLATE DATABASE_DEFAULT AS Place, ‘Arizona’ As State, Country FROM DEPT2 Edit: You may need it on every string if you get it in one places Select City COLLATE DATABASE_DEFAULT AS Place, State COLLATE … Read more