I think the trace is your best best, you should be able to see the command that is running as opposed to what you think is running..

CEWII

Well that explains a lot. unsigned byte = tinyint, not sure what the valid value is for integer though..

CEWII

Ok, for DT_NUMERIC length is greyed out but what are the values for precision and scale?

Also, you might consider screen printing the advanced editor screen with that field selected and...

How do you know step 1 is working, have you re-enabled the check constraints manually?

Also, I guess I would run a trace at this point to see what commands are...

Hold on David, I take exception to some things:

Too often it seems that database professionals appear to be defending the SQL status quo rather than standing up and acknowledging that...

If you change it to either DT_STR or DT_UI4 you will likely be ok, for the DT_STR you will be able to set the length, for DT_UI4 you won't it...

You might add a ";" after the use [database] statement.

Also is it just not working or is it returning any errors?

CEWII

Ok, valid question.. I will offer a solution that is dependent...

Is there a 1 in 10,000 chance I'd use it at some point sure.. But not without a substantial amount of fore-thought and then I'd still be inclined not...

I see ftp as more of a hinderance than a...

I figured you couldn't but it was simple enough to test yourself..

CEWII

G,

I got the parameter sniffing vibe off that article.. I have always had really good performance off these kinds of queries because I have avoided the causes of that....

Excellent point, so basically you don't even have that option..

CEWII

Those GO statements are important, they seperate one section from the other. Beyond that you really shouldn't do this. Although SQL supports it it is a bad practice...

You could try this:

SELECT *

FROM dbo.SomeTable

WHERE ( @Field1 IS NULL OR Field1 = @Field1 )

AND ( @Field2 IS NULL OR Field2 = @Field2...