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?

>A SQL Server instance is just an installed SQL Server. A machine (server or workstation) can have multiple instances of SQL Server. The first installed instance is generally the default instance. It's name is the same as the machine name. In your connection string, you just give the machine name as the data source.
>
>Any other instances of SQL Server installed on the same machine must be named and you use that name in the connection string to connect. For example, if the machine name is Fred and the instance is SQL2, in the connection string, you use "Data Source=Fred\SQL2".
>
>With SSMS, you can use the same install to connect to any SQL Server instances you have rights to. I have SSMS installed on my local PC and use it to connect to several SQL Server instances on the network.
>
>
>>Hi,
>>
>>I would to make sure that I am using the correct terms when writing to a customers. I need to write to them that they need to install a SQL Server on the application server or set up a SQL Instance with SSMS on the application server. My understanding is that "SQL Instance" would mean that the SQL Server is installed on another server with me being able to attach my application database to this SQL Instance.
>>Do I understand the "SQL Instance" term correctly?
>>
>>TIA