Comments
1 comment
-
Thanks for contacting Red Gate.
I don't think this is a bug - it looks like this happens when SQL Dependency tracker doesn't have enough information to work out who the object owner or schema it belongs to. On a normal, single-database project I did not see this behaviour, but if I added a second database, I start to see it.
For instance, I have to databases:
CrossDatabaseDependencyTest1
CrossdatabaseDependencyTest2
CrossDatabaseDependencyTest1 has a trigger:CREATE TRIGGER [dbo].[trigger] on [dbo].[table1] FOR INSERT, UPDATE AS SELECT data from CrossDatabaseDependencyTest2..Table1
The xml will say this about the dependent object:<Object>
<Name>[server].[CrossDatabasaDependencyTest1].[dbo].[Trigger]</Name>
<Type>Trigger</Type>
<Uses>
<Object>[server].[CrossDatabasaDependencyTest1].[dbo].[Table1]</Object>
<Object>[server].[CrossDatabasaDependencyTest1].[dbo].[dbo]</Object>
<UnresolvedObject>[server].[CrossDatabaseDependencyTest2]..[Table1]</UnresolvedObject>
</Uses>
</Object>
Add comment
Please sign in to leave a comment.
Is there a way to do the export and get the full names of these objects instead of the ".."?
Actually, if the export could strip off the [ServerName].[DatabaseName] portion of all the object names, that would be even better. Since it's the same for all objects in my export, there's no need for that to be listed hundreds of times within the XML.