Synonyms are a critical tool when working with a multi-server, multi-database RDBMS. Our database application consists of multiple databases, spread across both linked servers and in HAGs and nearly all combinations. Synonyms are a critical tool to reference the correct database objects (tables/views/procs) on different server in different databases constantly. When an object moves, or say an underlying linked server changes, you have to update the synonyms. Being able to search for the old server or database name in a synonym to ensure they've all been changed is a tedious task that sqlSearch could make so much easier. I realize that "dealing" with synonyms is likely problematic given how they are handled by sql server, but it's exactly because of their 'painful' nature that supporting them would really allow SQLSearch to really shine.
Jerry Langland
supported this idea
·
Synonyms are a critical tool when working with a multi-server, multi-database RDBMS. Our database application consists of multiple databases, spread across both linked servers and in HAGs and nearly all combinations. Synonyms are a critical tool to reference the correct database objects (tables/views/procs) on different server in different databases constantly. When an object moves, or say an underlying linked server changes, you have to update the synonyms. Being able to search for the old server or database name in a synonym to ensure they've all been changed is a tedious task that sqlSearch could make so much easier. I realize that "dealing" with synonyms is likely problematic given how they are handled by sql server, but it's exactly because of their 'painful' nature that supporting them would really allow SQLSearch to really shine.