Function is not created first when used as default value
flcdrg
Posts: 17 Bronze 2
We've noticed with Sql Compare 7.1.0.197 (and the SQL Comparison SDK) that it doesn't realise it needs to create a FUNCTION first if that function is used as a DEFAULT value for a TABLE definition.
Is this a known issue, and has it been corrected in a more recent version?
-dave
Is this a known issue, and has it been corrected in a more recent version?
-dave
Comments
Redgate Software