Newbie Constraints Problems
Brian Donahue
Posts: 6,590 Bronze 1
Hello Robert,
I'm sorry for the delay in answering you. There is a trick to getting
the FK dropped before scripting a table where the datatype changes in SQL
Compare. You'll find that if you select both of the objects linked by the
foriegn key and generate the migration script with the '!' icon, the key
will be dropped before anything is done to the table in the resulting
migration SQL.
Please let me know if you have any further questions.
Sincerely,
-Brian Donahue
"Robert LeRoy" <rleroy@cinci.rr.com> wrote in message
news:SziWaxBBDHA.1428@server53...
> I'm evaluating SQL Compare and have 22 tables that have changed. I
created
> the update scripts and tried to run them in Query Analyzer with multiple
> FK_Constriant issue. It seems that the generated doesn't drop the
> constraints before running. The odd thing is that at the bottom of the
> script I see it creating the contraints that weren't dropped at the
> beginning.
>
> Can I change datatypes with the tool? This seems to be one of the big
> issues. Especially, with fields that are part of a FK.
>
> Is this expected behavior? Is there something I can do to force the
> constraints to be better controlled?
>
> I'm using SQL2000 and have 182 tables in my database.
>
>
I'm sorry for the delay in answering you. There is a trick to getting
the FK dropped before scripting a table where the datatype changes in SQL
Compare. You'll find that if you select both of the objects linked by the
foriegn key and generate the migration script with the '!' icon, the key
will be dropped before anything is done to the table in the resulting
migration SQL.
Please let me know if you have any further questions.
Sincerely,
-Brian Donahue
"Robert LeRoy" <rleroy@cinci.rr.com> wrote in message
news:SziWaxBBDHA.1428@server53...
> I'm evaluating SQL Compare and have 22 tables that have changed. I
created
> the update scripts and tried to run them in Query Analyzer with multiple
> FK_Constriant issue. It seems that the generated doesn't drop the
> constraints before running. The odd thing is that at the bottom of the
> script I see it creating the contraints that weren't dropped at the
> beginning.
>
> Can I change datatypes with the tool? This seems to be one of the big
> issues. Especially, with fields that are part of a FK.
>
> Is this expected behavior? Is there something I can do to force the
> constraints to be better controlled?
>
> I'm using SQL2000 and have 182 tables in my database.
>
>
This discussion has been closed.
