It looks as though you are suffering from this SQL Compare issue
. Since Dependency Tracker uses version 5.3 of the SQL Compare Engine logic, the problem will not be worked around until Dependency Tracker is built using the new components, which should happen in a few weeks.
To identify whether or not this is the issue, you may run the following query in Management Studio:
- Code: Select all
select c.text from syscomments c inner join sysobjects o on o.id=c.id where o.name='rpt_MyView'
This should show whether there is a mismatch between the name of the view in the metadata and the actual definition that created the view (the latter being the one Dependency Tracker uses).
The only workaround at this time would be to drop and re-create the view with the proper name.