Good explanation of the self-blocking processes. Also, for your deadlocks, here's a good link to help :http://www.sqlservercentral.com/articles/Performance+Tuning+and+Scaling/tracingdeadlocks/1324/

Just some inside info on what's happening here. When you attempt to insert a '' into a datetime column, SQL Server must CAST the blank value to datetime. ...

Here's another approach w/o the PIVOT.

SET NOCOUNT ON

DECLARE @table1 TABLE(region_id int, region varchar(15))

INSERT INTO @Table1

SELECT 1, 'North East' UNION ALL

SELECT 2, 'South East' UNION ALL

SELECT 3, 'South West'

DECLARE @Table2...

Well, first of all, everyone's opinion of rich differs. Making 150 K per year is far from rich. I do know that there are a couple of things...

Uh, you don't need a script task for this. This is an extremely simple operation to do. Use the ForEach Loop Container and place a File System Task...

This is entirely too generic for anyone to help you out. We'll need some sort of table schema, sample data, and an example of what you are talking about...

If it is NULL, why not just set it to the new XML value without going through the XML DML?

DECLARE @ProductBase TABLE (ID int IDENTITY(1,1), CrossSell xml)

INSERT INTO @ProductBase

DEFAULT VALUES

SELECT...

Here's a link to the OP's other post on this same topic for reference, but let's use this current thread as the only one going forward.

Other thread:http://www.sqlservercentral.com/Forums/Topic582789-8-1.aspx

Please don't cross post....

Let's continue this thread here:http://www.sqlservercentral.com/Forums/Topic582739-338-1.aspx

Continuing the cross-posted thread from here: http://www.sqlservercentral.com/Forums/Topic582839-149-1.aspx#bm582875

anupamabr,

If when you select the XML value, it returns the word NULL, it means that there is no value. If you inserted...

Please don't cross post.

Continue discussion HERE:

http://www.sqlservercentral.com/Forums/Topic582804-149-1.aspx

You may try the Conditional Split or Multicast Data Flow Transformations (or a combination of both).

The issues that everyone has raised here for correct placement of clustered indexes are all valid. It is a best practice to have a clustered index on all tables,...

Letting you know that it is best practice to do that kind of work in the reporting tool is helping you. That is what those types of tools were...

Well, the error means exactly what it says...you can't compare the XML data type like that. I see that you declare the XML variable, but never assign it a...