Comments
3 comments
-
Hi, same issue here.
-
Hi anna.p
Thanks for reaching out to us regarding this, I'm sorry you are seeing this issue with SQL Compare!
Just as an initial question, what version of SQL Compare are you seeing this in?
I don't think this will be playing any part in the behavior you're seeing here, but do you have 'Ignore Bindings' checked or unchecking within your project options?
-
Had a resurfaced issue - https://forum.red-gate.com/discussion/88871/dropping-schemabindingTried 'Ignore Bindings' and the script generates
)
RETURNS Table
WITH
RETURN
(
SELECT
We have to hand edit the script to change WITH to 'AS'
Add comment
Please sign in to leave a comment.
We have a lot of views with SCHEMABINDING.
It often happens that SQL Compare will miss a dependency and attempt to alter a table referenced by a schema bound view without first altering the view to remove the SCHEMABINDING.
This doesn't happen all the time; I'd say 70% of the dependencies are caught and 30% aren't.
How does SQL Compare determine when a view needs to be altered to remove SCHEMABINDING? Is there some system table it checks? If so, maybe we have inconsistencies in that system table?
It's getting a little frustrating having to add 2 ALTER VIEW statements manually to a bunch of build scripts... :-/
I'm normally using the GUI, by the way.
Any ideas would be appreciated!