Protect and invirible Database from each other

Hi,
I'm using Windows 2000 Server + SQL Server 2000 + updated SP
This server is our Web Hosting services and we have many database in SQL Ser
ver.
Each databases are belonged to each customer domains in this Server.
All customers work with SQL Server by using SQL Enterprise Manage to connect
to the Server via TCP/IP.
My problem is that, after customers connect to the SQL Server, they can see
every Databases' name and table name although I'd set the right of each cust
omer to be able to see only their own database.
I'd ask many SQL Experts but they said that if I used SQL Enterprise manager
to remote connect to the SQL Server, this senario could not be protected an
d let me ask Microsoft.
Using SQL Enterprise Manager is the easiest way for my customer to manage th
eir database, so if I let them use the SQL command line to connect to the SQ
L Server, no customers will use my service.
Please help.
Regards,
NeungThere is no way currently to stop them from seeing the other databases. But
unless you give them specific permissions they can not access or view the
data in them.
Andrew J. Kelly SQL MVP
"Neung" <Neung@.discussions.microsoft.com> wrote in message
news:F5F3F38C-8F8B-499F-8C9C-7BE19D350C9A@.microsoft.com...
> Hi,
> I'm using Windows 2000 Server + SQL Server 2000 + updated SP
> This server is our Web Hosting services and we have many database in SQL
Server.
> Each databases are belonged to each customer domains in this Server.
> All customers work with SQL Server by using SQL Enterprise Manage to
connect to the Server via TCP/IP.
> My problem is that, after customers connect to the SQL Server, they can
see every Databases' name and table name although I'd set the right of each
customer to be able to see only their own database.
> I'd ask many SQL Experts but they said that if I used SQL Enterprise
manager to remote connect to the SQL Server, this senario could not be
protected and let me ask Microsoft.
> Using SQL Enterprise Manager is the easiest way for my customer to manage
their database, so if I let them use the SQL command line to connect to the
SQL Server, no customers will use my service.
> Please help.
> Regards,
> Neung|||Thanks and hope it will be solved in the next version.
Regards,
Neung
"Andrew J. Kelly" wrote:

> There is no way currently to stop them from seeing the other databases. B
ut
> unless you give them specific permissions they can not access or view the
> data in them.
> --
> Andrew J. Kelly SQL MVP
>
> "Neung" <Neung@.discussions.microsoft.com> wrote in message
> news:F5F3F38C-8F8B-499F-8C9C-7BE19D350C9A@.microsoft.com...
> Server.
> connect to the Server via TCP/IP.
> see every Databases' name and table name although I'd set the right of eac
h
> customer to be able to see only their own database.
> manager to remote connect to the SQL Server, this senario could not be
> protected and let me ask Microsoft.
> their database, so if I let them use the SQL command line to connect to th
e
> SQL Server, no customers will use my service.
>
>|||Yes, SQL 2005 has a lot of improvements in this area.
Andrew J. Kelly SQL MVP
"Neung" <Neung@.discussions.microsoft.com> wrote in message
news:032A5CFE-D0D9-4727-8032-707D90436D80@.microsoft.com...[vbcol=seagreen]
> Thanks and hope it will be solved in the next version.
> Regards,
> Neung
>
> "Andrew J. Kelly" wrote:
>
But[vbcol=seagreen]
the[vbcol=seagreen]
SQL[vbcol=seagreen]
can[vbcol=seagreen]
each[vbcol=seagreen]
manage[vbcol=seagreen]
the[vbcol=seagreen]|||> My problem is that, after customers connect to the SQL Server, they can
see every Databases' name and table name although I'd set the right of each
customer to be able to see only their own database.
Although database names are visible, I would not expect users to be able to
see other database contents unless they have explicitly been granted access
or the 'guest' user is enabled in the other databases.
Hope this helps.
Dan Guzman
SQL Server MVP
"Neung" <Neung@.discussions.microsoft.com> wrote in message
news:F5F3F38C-8F8B-499F-8C9C-7BE19D350C9A@.microsoft.com...
> Hi,
> I'm using Windows 2000 Server + SQL Server 2000 + updated SP
> This server is our Web Hosting services and we have many database in SQL
Server.
> Each databases are belonged to each customer domains in this Server.
> All customers work with SQL Server by using SQL Enterprise Manage to
connect to the Server via TCP/IP.
> My problem is that, after customers connect to the SQL Server, they can
see every Databases' name and table name although I'd set the right of each
customer to be able to see only their own database.
> I'd ask many SQL Experts but they said that if I used SQL Enterprise
manager to remote connect to the SQL Server, this senario could not be
protected and let me ask Microsoft.
> Using SQL Enterprise Manager is the easiest way for my customer to manage
their database, so if I let them use the SQL command line to connect to the
SQL Server, no customers will use my service.
> Please help.
> Regards,
> Neung