Re: Password MDF
- From: "Julián Sanz García" <jsanz@xxxxxxxxxxxx>
- Date: Wed, 24 Oct 2007 18:11:25 +0200
Hi Uri,
Thank you for your answer but it doesn't work because I can connect to SQL
Server 2005 Management Studio with Windows Authetication and I still see
"dbteste" database and all his objects, so if I distribute this database
with a desktop application and one user has SQL Server 2005 Management
Studio, this user will see all exiting data.
Best regards
"Uri Dimant" <urid@xxxxxxxxxxx> escribió en el mensaje
news:OM2HiRlFIHA.1324@xxxxxxxxxxxxxxxxxxxxxxx
Hi
It works perfectly if the user is the owner of the database. Look
that .
. Create a new SQL login "login1"
. Create a user named "login1" in master database
. Grant CREATE DATABASE to login1
. While impersonating login1, create a database called "dbteste"
. Revoke CREATE DATABASE permission from login1
. Revoke VIEW ANY DATABASE permission from PUBLIC
. Register this server as login1
. From the "login1" session, expand database tree. Now, you should see
master, tempdb, dbteste
. Grant VIEW ANY DATABASE to PUBLIC
. From the "login1" session, you should see all the databases
"Julián Sanz García" <jsanz@xxxxxxxxxxxx> wrote in message
news:upUufJlFIHA.3672@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
¿Are there any way to protect a database that is reditributed with a
desktop application? I want to protect this database with an user and a
password, something like access, but with SQL Server 2005, if you have
SQL Server 2005 Management Studio, you can access without any problems
and you can see all database objects.
Thanks a lot
.
- References:
- Password MDF
- From: Julián Sanz García
- Re: Password MDF
- From: Uri Dimant
- Password MDF
- Prev by Date: Re: Password MDF
- Next by Date: Re: Password MDF
- Previous by thread: Re: Password MDF
- Next by thread: Re: Password MDF
- Index(es):
Relevant Pages
|
|