Both process request an exclusive lock on partitions on table Item.   The deadlock does not occur on the table variables.  By the way Do you really need to use the...

It will show you details only on plans that exist in the query cache.  As soon as a query plan is being deleted from the query plan, you won't be...

Actually it is a bug.  It doesn't depend on the number of partitions.  I can have only 2 partitions and the optimizer will do a table scan instead of an...

Unfortunately there is an old bug that for some reason Microsoft is not fixing.  When using top clause or min or max aggregation functions on a partitioned table, SQL Server...

Another way is to specify the full XML path in the where clause (the nodes operator) and then get the value of ID:

SELECT 
XC.value('.[1]', 'int')
FROM
  ...

You need to write throw also in the inner procedures.  If they have a catch block without throw in it, you won't see the error.  Also I don't know how...

The catch section hides the error message.  If you'll add throw to it, it will send you the full error message that includes the place that the error occurred.  Check...

• This reply was modified 4 years, 8 months ago by  Adi Cohn.

You can also create a persisted computed column for FUNCAveMile([Mileage]) and index that column.  This way you won't even have to modify the query.  Of course if you can just...

I don't think that the profiler will disappear soon, but it also will not be develop to support new features.  Extended events on the other hand will continue to...

You didn't write any details about what you are doing (a select statement with for xml clause? selecting a huge xml column? using xquery to create or modify an...

Here is one more way:

declare @t table (id char(1), cat char(5))
insert into @t (id, cat)
select 'a', 'info'
union select 'b', 'info'
union select 'c',...

You need another END for the inner case:

SELECT
    CASE WHEN CONFIG.PremiumSignShowData>0
    THEN CASE SIGN (ISNULL(resultPremium,0))
        WHEN '-1' THEN '-'
        ELSE '+'

I had the same situation when I created native compiled dropped procedures with SQL Server 2014.  Was hoping that with SQL Server 2016 it will be supported, but it seems...

I would seriously consider redesigning so both databases will use the same primary key and then I'd simply use replication. If this is not possible, then you can develop...