Re: Protect and invirible Database from each other

From: Dan Guzman (danguzman_at_nospam-earthlink.net)
Date: 07/17/04 

Date: Sat, 17 Jul 2004 09:18:10 -0500

> 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

Relevant Pages

  • Re: Assume SQL Server Rights for apps, any cons?
    ... Since your customer is the sysadmin on his SQL Server box, ... >administrates the underlying SQL Server 2000 database by himself. ... >wants that my software assumes the user rights automatically from the SQL ... >My application offers a GUI to manage customers. ...
    (microsoft.public.dotnet.framework)
  • Re: SQL Server Royalty
    ... would the customer, but this "royalty premium"... ... > to work on its database. ... > in house applications using SQL Server to other databases ... >>> customers this 'premium' if customers want to use their ...
    (microsoft.public.sqlserver.clients)
  • Re: MS Access DAO -> ADO.NET Migration
    ... William Vaughn ... Microsoft MVP ... Hitchhiker's Guide to Visual Studio and SQL Server ... My migration app works building a SSCE database file with imported data ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Word 2003/Access2000/SQLSVR
    ... SQL server being where the data is held and this is accessed through a MS ... entire database and that may be say a record for Berkshire. ... "Peter Jamieson" wrote: ... replaced with the first record on the table in use. ...
    (microsoft.public.word.mailmerge.fields)