Comments
4 comments
-
I'm sorry you have encountered this issue. I will be responding to you via email with the information relevant to troubleshooting this problem.
Thanks! -
Note: this *only* happens when you use a filtered index.
Using a WITH clause alone works OK. But not when you have a WITH and WHERE clause.
So there's no confusion... -
Thank you. I have logged a bug with our development team ( SDC-1502 ).
-
One year later... any update please?
Add comment
Please sign in to leave a comment.
The WHERE and WITH clauses are the wrong way around
What is generated:
This means that I have to use SQL Compare to fix the schema after synchronizing data and can't trust SQL Data Compare
Can this be fixed please?