Help - All Users can Access All Databases

Dan wrote:
> Hello. I am using SQL Server 2005 Std. 32bit on Windows 2003 R2. I am
> having an issue where, when I create a new user, even before I assign them
> any rights they can connect to any database in my SQL instance and read/wr
ite
> everywhere. I can't imagine this is by design.
> Anyone know whats going on here?
http://msdn.microsoft.com/msdnmag/i...ServerSecurity/Hello. I am using SQL Server 2005 Std. 32bit on Windows 2003 R2. I am
having an issue where, when I create a new user, even before I assign them
any rights they can connect to any database in my SQL instance and read/writ
e
everywhere. I can't imagine this is by design.
Anyone know whats going on here?|||Dan wrote:
> Hello. I am using SQL Server 2005 Std. 32bit on Windows 2003 R2. I am
> having an issue where, when I create a new user, even before I assign them
> any rights they can connect to any database in my SQL instance and read/wr
ite
> everywhere. I can't imagine this is by design.
> Anyone know whats going on here?
http://msdn.microsoft.com/msdnmag/i...ServerSecurity/|||Are any of these users in Windows groups (such as the administrators group)?
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:D49A8E3D-1788-48E6-B4D6-F42F6A9B16C3@.microsoft.com...
> Hello. I am using SQL Server 2005 Std. 32bit on Windows 2003 R2. I am
> having an issue where, when I create a new user, even before I assign them
> any rights they can connect to any database in my SQL instance and
> read/write
> everywhere. I can't imagine this is by design.
> Anyone know whats going on here?|||We ran into a similar issue. The issue for us is that we granted
permissions to the public role, and since the guest account is enabled
by default, everyone has access to that database via the guest role.
Since the public role includes guest, granting public role gives them
access. I dont know if this is the scenario you have encountered, but
it can be handled by not using the public role and just granting
permissions to roles or groups that you are in control of.|||Are any of these users in Windows groups (such as the administrators group)?
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:D49A8E3D-1788-48E6-B4D6-F42F6A9B16C3@.microsoft.com...
> Hello. I am using SQL Server 2005 Std. 32bit on Windows 2003 R2. I am
> having an issue where, when I create a new user, even before I assign them
> any rights they can connect to any database in my SQL instance and
> read/write
> everywhere. I can't imagine this is by design.
> Anyone know whats going on here?|||We ran into a similar issue. The issue for us is that we granted
permissions to the public role, and since the guest account is enabled
by default, everyone has access to that database via the guest role.
Since the public role includes guest, granting public role gives them
access. I dont know if this is the scenario you have encountered, but
it can be handled by not using the public role and just granting
permissions to roles or groups that you are in control of.

HELP

SQL will not allow me to create a secondary file group that replaces the
primary. I have no space to run queries.
--
Regards,
Jamie
"thejamie" wrote:

> When we setup SQL 2005, it was setup to house the log files on a larger
> drive. It was not setup to house the tempdb files when they grow to a la
rge
> size. We are running out of disk space on the C:\ drive. Is it possible
to
> move this without reinstalling SQL Server 2005? For that matter, if I mus
t
> reinstall, can the tempdb be placed in an alternate location (other than t
he
> C drive)?
> --
> Regards,
> JamieHey, I am also facing the similar problem, how can I resolve this, please I
need your urgent response.
I am working on this now.. I got this problem as a result of migrating the d
ata from one data base to another back up database.
From http://www.developmentnow.com/g/118...467001/HELP.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com