Comments
1 comment
-
OK, I have solved the problem. My database was in SQL 2000 compatibility mode. This was intentional, due to some non-ANSI joins, but I had forgotten. I would still have expected this tool to recognise this fact and generate a working script, or at least alert me to this, but, anyway, problem solved.
P
Add comment
Please sign in to leave a comment.
It generates code like:
but this always returns:
.
The new schema exists, as I previously ran:
And it appears in a list when I run