Preventing SQL Compare from DROP and CREATE SYNONYM
tobin
Posts: 8 New member
in SQL Compare
Hey all,
We have a reporting database where on the live server we point our synonyms at [Production].[dbo].[tblName], but on our replicated server we use [Reports].[Production].[tblName].
When I try to use the sql compare cmdline tool to deploy a view or stored procedure, it seems to want to DROP and CREATE SYNONYM, but it uses the database, schema and table name from the source database.
Is there a way to prevent it from deciding to DROP and CREATE the synonym dependencies?
We have a reporting database where on the live server we point our synonyms at [Production].[dbo].[tblName], but on our replicated server we use [Reports].[Production].[tblName].
When I try to use the sql compare cmdline tool to deploy a view or stored procedure, it seems to want to DROP and CREATE SYNONYM, but it uses the database, schema and table name from the source database.
Is there a way to prevent it from deciding to DROP and CREATE the synonym dependencies?
Tagged:
Answers
Yes, you can use a filter file that excludes synonyms.
For more details please see: https://documentation.red-gate.com/sc/using-the-command-line/switches-used-in-the-command-line#Switchesusedinthecommandline-/Filter
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
I appreciate you getting back to me.