Sometimes (like this instance with nearly 200 columns) it is easier to start over. Starting over works.

I'm seeing something similar... no answer for you.

My error lines appear as follows:

[DTS.Pipeline] Information: "component "Error Destination" (6253)" wrote 3 rows.

[DTS.Pipeline] Information: "component "Flat File Destination" (51695)" wrote 0 rows.

[DTS.Pipeline]...

Date questions are fun

I did not think it was possible to make a more off topic and negative statement that made less sense.

The question was about DDL and data storage.

You are making negative...

Jamie - It was my understanding that this question was about how data is stored in the data pages. What did you see that made you think about query optimization?...

good question

I selected four items correctly (I thought) but still received a wrong answer. I may need to get a new click finger or something.

But this was a...

For me, CXPACKET was fixed by not allowing SQL to have all the processors and all the memory. I removed one of the processors (Properties | Processor of the...

ansi?

char - characters...

The brain sleeps when it runs out of energy. Often it is smarter than we are.

No, char(8) is better. Like I said, sometimes I just prefer not to have to think about it.

I prefer something I can rely on to work for all cases with dates... my favorite is

CONVERT(varchar(8),getdate(),112)='20110215'

because it is easy to remember and there are not special characters...

Here is a better example:

http://connect.microsoft.com/SQLServer/feedback/details/573675/error-converting-data-type-varchar-to-datetime

I agree, the 'CORRECT' answer is that we would hope that SQL Server has not put out...

What happens when:

Declare @dt datetime2

SET @dt='1752-09-09'

DECLARE @dt2 datetime

DECLARE @dt3 varbinary

SET @dt3=CONVERT(VARBINARY,@dt)

SELECT @dt3

SELECT cast(CAST(@dt3 AS NVARCHAR) AS varbinary)

SELECT CONVERT(DATETIME2,cast(CAST(@dt3 AS NVARCHAR) AS varbinary))

SET