MicrosoftMicrosoftWhat if there are internal dependencies on such synonyms?
Wouldn't dropping them break the verification as well?
And let's say that instead of dropping synonyms, you'd "redirect" them towards an internal table or object.
But then, wouldn't it still cause verification errors if there are dependencies that rely on a specific table/column structure?
Not to mention the obvious impact on business logic during production.
Here's a big idea for the Microsoft team which should make this much simpler:
Add support for the "VerifyExtraction=False" parameter for the "Export" action as well and not just the "Extract" action.
P.S.
You also have a syntax error here (CREATE SYNONYM written twice):
EXEC SP_EXECUTESQL N'CREATE SYNONYM [dbo].[ExternalTable2] CREATE SYNONYM [dbo].[ExternalTable2] FOR [LinkedServerName].[DatabaseName].[SchemaName].[ExternalData2]'
Generally, I'd expect a better solution than hard-coding the creation code per each individual synonym.
Why not use the metadata in sys.synonyms to auto-generate the creation code for all 3-part-name and 4-part-name synonyms in advance?
