>>First, thank you for the explanation. Here is what I need to clarify for myself. For example, the customer (big organization) has a SQL Server installed on some server. They have many databases on this server. Now then need to allow me to attach my database to this server and maintain it. But they don't want me to see other databases or make any changes to them. So they have to install SSMS on my application server (where my VFP app resides). And when I use this SSMS I can attach my database and maintain it; without seeing other databases. So how do they (the customer IT) do that; create SSMS that only allows me to view/maintain one database?
>
>See also
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/a989ca87-660d-41c4-9dac-70b29a83ddfb/hide-database-names-from-unauthroized-users-in-ssms?forum=sqlsecurityThank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
