Re: Permissions on a database

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Rick Sawtell (r_sawtell_at_hotmail.com)
Date: 10/20/04 

Date: Wed, 20 Oct 2004 14:06:02 -0700

> > If they are good, they will create their objects with the dbo.ObjectName
> > prefix. If they are not good, then you will end up with objects that
> > look
> > like Rick.Table1.
>
> Would this be a problem for me down the line?

Yes! dbo should own all of the objects in the database. Period.

> > You could do and sp_addalias and mark them as dbo in the database.
>
> What does that do?

It maps them into the database as a dbo rather than as their UserName who is
a member of the db_owners role.

If they are mapped as the dbo, they can do things like: CREATE TABLE Frog
This will make it dbo.Frog by default.

If they are mapped in as a User who is a member of db_owners role, then the
same CREATE TABLE Frog would come back as
UserName.Frog rather than dbo.Frog.

> > This should do what you want it to. By using the Windows account, you
> > also
> > get the benefits of restricting everything else that they might wish to
do
> > on your server as well as evaluate log in times, log outs, minimum
> > password
> > lengths and so forth.
>
> I didn't want to give them access to the Windows server at all. That was
> why I was having them do Sql Server Authentication. Do I also have to
give
> them Windows Access also? If that is the case, I why would anyone use the
> Sql Server Authentication anyway?

If you don't give them access to the Windows computer how do you expect them
to connect to the SQL Server? The SQL Authentication is used to allow SQL
Server to authenticate access to SQL Server rather than Windows
authenticating access to SQL Server.

> I am just trying to figure out the best way to do this.
>
> Thanks,

=)

Rick

> Tom.
> >
> >
> > HTH
> >
> > Rick Sawtell
> > MCT, MCSD, MCDBA
> >
> >
> >
>
>

Relevant Pages

  • Re: Microsoft Web Data Administrator
    ... > login USING WINDOWS NT Integrated Security.... ... if you can not connect using SQL Server authentication at all, ...
    (microsoft.public.sqlserver.msde)
  • Re: 2000k connect from outside domain
    ... You cannot fill in the user name and password because by doing so you are telling the login process to use SQL Server Authentication rather than windows authentication, and you would need a SQL Server authenticated login to do so. ...
    (microsoft.public.sqlserver.connect)
  • Re: Changing passwords / Blocking SA login attempts
    ... Changing a Windows password is always completely invisible to SQL Server. ... The Windows login is completely separate from a SQL Server login, ... If you are using SQL Server Authentication, then one doesn't even have to ...
    (microsoft.public.sqlserver.security)
  • Programmatically create DSN usind SQL Server Authentication
    ... I am trying to programmatically create a DSN on a target system for SQL ... Server using SQL Server Authentication. ... is off-topic for my purpose because it only shows Windows authentication. ...
    (microsoft.public.sqlserver.odbc)
  • Re: Connexion to SSIS
    ... A way to verify it the account in question to the local admins and try ... If you do not want to, can use proxy accounts. ... only SQL Server authentication and use it to connect my remote client to the ... SQLServer Account by SQL Server Authentication? ...
    (microsoft.public.sqlserver.dts)