Logins

From: John Kraeck (jkraeck@hillier.com)
Date: 09/09/02 

From: "John Kraeck" <jkraeck@hillier.com>
Date: Mon, 9 Sep 2002 11:52:11 -0400

We have a SQL Server login which is used by two applications, to access two
separate databases on the server.

When I run sp_helplogins on this login id, I get exactly what I expect: the
master information for the server (suid, default database,etc.), and the
information for the databases for which the login has been added as a user.
When I view the properties of this login from the Enterprise Manager, I
expect the databases to be checked on the "Database Access" tab and the User
information to be displayed. Nothing is displayed. We are beginning to
experience random access problems, and connection timeouts on the server,
and I am wondering if this could be having any effect.

Thanks,
   John Kraeck

Relevant Pages

  • Re: Remove/Add BUILTINAdministrators 2000 sp4
    ... I have seen a windows group referred to as a LOGIN for sql server in the ... the databases, and so it makes it dbo on all databases again. ...
    (microsoft.public.sqlserver.security)
  • Re: Remove/Add BUILTINAdministrators 2000 sp4
    ... detected that this login has permissions....etc this login ... be mapped to dbo. ... sysusers in the user databases and syslogins in master. ... I have seen a windows group referred to as a LOGIN for sql server in the ...
    (microsoft.public.sqlserver.security)
  • Re: Remove/Add BUILTINAdministrators 2000 sp4
    ... any of the databases. ... exist anywhere in sql server either. ... detected that this login has permissions....etc this login ... be mapped to dbo. ...
    (microsoft.public.sqlserver.security)
  • Re: Remove/Add BUILTINAdministrators 2000 sp4
    ... Server, it some how knows that on this server, it use to be the dbo in all ... the databases, and so it makes it dbo on all databases again. ... via this LOGIN ...
    (microsoft.public.sqlserver.security)
  • Re: MULTIPLE ACCESS DATABASE BACK-ENDS ON THE SERVER - VIRTUAL MULTIUSER
    ... from the different databases into common tables and running reports or form ... > a very strong server. ... > crucial tables from the separate databases will ... > "Company database" will not exced 2 MB ...
    (microsoft.public.access.formscoding)