We need to use SELECT and put the "WITH namesapce" in the outside of the assignement, and use TYPE directive in the SELECT for XML statement The following should work:

ALTER PROCEDURE [dbo].[uwmSP_GetScenarioPreStage]...

The purpose of the "inlcuded columns" in the index is to remove the key lookup. In the test4 of the article, it achieved this by removing those columns (GroupName, ParentGroupName,ParentGroupID) in the...

The hard limit of partition number is 999.

I just sent an email to Steve about the broken of the link to the scripts.

If it's not possible to fix the link, I can send the scripts to your...

I guess you turned SET IMPLICIT_TRANSACTIONS to ON in the query window (connection). When it's ON, whenever you start a SELECT, INSERT, UPDATE, DELETE .. etc statements, SQL server starts...

Thanks everyone.

The scripts were all submitted to SQLCentral.com with the article. I am not sure why the link was broken.

To Charles Kincaid:

What...

I summarized the solution to the MSDTC issue in one of my blog. Take a look and see whether it's helpful.

http://p-sql.spaces.live.com/?_c11_blogpart_blogpart=blogview&_c=blogpart&partqs=amonth%3d2%26ayear%3d2007

Check out this:

http://p-sql.spaces.live.com/?_c11_blogpart_blogpart=blogview&_c=blogpart&partqs=amonth%3d10%26ayear%3d2006

If the result of the subquery contains NULL value and ANSI NULL is set ON, the query result of IN + NOT IN does not equal to the statement...

1) Indexes are for the table, not for partitions of the table. So you can't keep the index for the last partition and drop the same index for the older...

1) Indexes are for the table, not for partitions of the table. So you can't keep the index for the last partition and drop the same index for the older...

SQL server does not support time zone when cpnverting xml dateTime data type.

If you truncate the time zone part from the date time string (-5:00), the converted data time will have the...

SQL server converts the result of top expression to float. This results in a wrong number of records returned. You can confirm this by the execution plan.

Anyway, it sounds a...

Kunal,

You said in your first post that you had this issue in SQL2005 Enterprise endition, and my answer is definitley for sql 2005.

For SQL 2000, I have no idea.

SQL server has plan guides, which is designed exactly to solve the issue you are facing by a vendors queries. E.g. if the vender's client sends a quey:

SELECT * FROM Sales.SalesOrderHeader...

For databases in replication, multiple servers are involved (publisher, distributer, and subscribers). you need to upgrade the servers in the right order. The SP2 readme has the details.