they don't really get executed first or second.... it's more like ALL constraints, including whether a column is nullable or not, all get evaluated prior to the the insert or update...if any constraint gets violated, an error is raised.

while it's true that in your example, if i put 100 dollars in the column, and there are two different constraints, one checking > 800 and the other for > 1000, only one of them is going to be returned, but i don't believe you can decide which occurs first.

it could be on my server, the check constraint returns the error, and on your server, the bind rule constraint returns as the error.

I've never seen any info on the order of precedence.

FYI, when i try to insert, the rule raises an error on my machine:

insert into account([CHECK_IN_AMT]) values (100)

Msg 513, Level 16, State 0, Line 1

A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database 'tempdb', table 'dbo.ACCOUNT', column 'CHECK_IN_AMT'.

The statement has been terminated.