I would like to be able to do something like this:
use mydb
exec sp_grantdbaccess 'localhost\Users'
go
When I do, I get this error msg:
Windows NT user or group 'localhost\Users' not found. Check the name
again.
The error message implies that I should be able to add a group.
A co-worker read on the web somewhere that this should work:
exec sp_grantdbaccess 'localhost\domain Users'
but it also fails the same way.
Any help would be appreciated,
TIA,
DaveDid you add that group as a login to SQL Server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dave" <kaatzd@.hotmail.com> wrote in message
news:1155062014.520009.304330@.b28g2000cwb.googlegroups.com...
>I would like to be able to do something like this:
> use mydb
> exec sp_grantdbaccess 'localhost\Users'
> go
> When I do, I get this error msg:
> Windows NT user or group 'localhost\Users' not found. Check the name
> again.
> The error message implies that I should be able to add a group.
> A co-worker read on the web somewhere that this should work:
> exec sp_grantdbaccess 'localhost\domain Users'
> but it also fails the same way.
> Any help would be appreciated,
> TIA,
> Dave
>|||Users is a predefined group, my understanding was that SQL would
recognize it.
Be that as it may, someone else in my company gave me the solution:
exec sp_grantdbaccess 'NT AUTHORITY\Authenticated Users'
and then I also needed to add above users to a role for my db, like so:
exec sp_addrolemember 'db_datareader', 'NT AUTHORITY\Authenticated
Users'
Thanks,
Dave
Tibor Karaszi wrote:
> Did you add that group as a login to SQL Server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dave" <kaatzd@.hotmail.com> wrote in message
> news:1155062014.520009.304330@.b28g2000cwb.googlegroups.com...
> >I would like to be able to do something like this:
> >
> > use mydb
> > exec sp_grantdbaccess 'localhost\Users'
> > go
> >
> > When I do, I get this error msg:
> > Windows NT user or group 'localhost\Users' not found. Check the name
> > again.
> >
> > The error message implies that I should be able to add a group.
> >
> > A co-worker read on the web somewhere that this should work:
> >
> > exec sp_grantdbaccess 'localhost\domain Users'
> >
> > but it also fails the same way.
> >
> > Any help would be appreciated,
> > TIA,
> > Dave
> >
Showing posts with label localhost. Show all posts
Showing posts with label localhost. Show all posts
Tuesday, March 27, 2012
Can I grant a group access to my db
I would like to be able to do something like this:
use mydb
exec sp_grantdbaccess 'localhost\Users'
go
When I do, I get this error msg:
Windows NT user or group 'localhost\Users' not found. Check the name
again.
The error message implies that I should be able to add a group.
A co-worker read on the web somewhere that this should work:
exec sp_grantdbaccess 'localhost\domain Users'
but it also fails the same way.
Any help would be appreciated,
TIA,
DaveDid you add that group as a login to SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dave" <kaatzd@.hotmail.com> wrote in message
news:1155062014.520009.304330@.b28g2000cwb.googlegroups.com...
>I would like to be able to do something like this:
> use mydb
> exec sp_grantdbaccess 'localhost\Users'
> go
> When I do, I get this error msg:
> Windows NT user or group 'localhost\Users' not found. Check the name
> again.
> The error message implies that I should be able to add a group.
> A co-worker read on the web somewhere that this should work:
> exec sp_grantdbaccess 'localhost\domain Users'
> but it also fails the same way.
> Any help would be appreciated,
> TIA,
> Dave
>|||Users is a predefined group, my understanding was that SQL would
recognize it.
Be that as it may, someone else in my company gave me the solution:
exec sp_grantdbaccess 'NT AUTHORITY\Authenticated Users'
and then I also needed to add above users to a role for my db, like so:
exec sp_addrolemember 'db_datareader', 'NT AUTHORITY\Authenticated
Users'
Thanks,
Dave
Tibor Karaszi wrote:[vbcol=seagreen]
> Did you add that group as a login to SQL Server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dave" <kaatzd@.hotmail.com> wrote in message
> news:1155062014.520009.304330@.b28g2000cwb.googlegroups.com...
use mydb
exec sp_grantdbaccess 'localhost\Users'
go
When I do, I get this error msg:
Windows NT user or group 'localhost\Users' not found. Check the name
again.
The error message implies that I should be able to add a group.
A co-worker read on the web somewhere that this should work:
exec sp_grantdbaccess 'localhost\domain Users'
but it also fails the same way.
Any help would be appreciated,
TIA,
DaveDid you add that group as a login to SQL Server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Dave" <kaatzd@.hotmail.com> wrote in message
news:1155062014.520009.304330@.b28g2000cwb.googlegroups.com...
>I would like to be able to do something like this:
> use mydb
> exec sp_grantdbaccess 'localhost\Users'
> go
> When I do, I get this error msg:
> Windows NT user or group 'localhost\Users' not found. Check the name
> again.
> The error message implies that I should be able to add a group.
> A co-worker read on the web somewhere that this should work:
> exec sp_grantdbaccess 'localhost\domain Users'
> but it also fails the same way.
> Any help would be appreciated,
> TIA,
> Dave
>|||Users is a predefined group, my understanding was that SQL would
recognize it.
Be that as it may, someone else in my company gave me the solution:
exec sp_grantdbaccess 'NT AUTHORITY\Authenticated Users'
and then I also needed to add above users to a role for my db, like so:
exec sp_addrolemember 'db_datareader', 'NT AUTHORITY\Authenticated
Users'
Thanks,
Dave
Tibor Karaszi wrote:[vbcol=seagreen]
> Did you add that group as a login to SQL Server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Dave" <kaatzd@.hotmail.com> wrote in message
> news:1155062014.520009.304330@.b28g2000cwb.googlegroups.com...
Wednesday, March 7, 2012
Can connect to only One instance from another computer
We can only connect to only 1 instance, either the default localhost or the
named instance from another client.
For example on my computer the other client can connect to the localhost and
the other instance name such as server\instancenames cannot be connected. On
the other computer that does not have the default instance, the client can
only connect to one instance such as server\instancename.
The error message is the same as when sql cannot connect.
Mike
What version, edition of SQL Server? What is the exact error
message? What are you using to try to connect - application,
SQL Tools, DSN? Did you check for what instances are
running? The clients that can't connect to a named instance
- did you check their MDAC versions? Can you connect to
default and named instances when on the box where the
instances are running?
-Sue
On Thu, 23 Mar 2006 07:00:29 -0800, Mike9900
<Mike9900@.discussions.microsoft.com> wrote:
>We can only connect to only 1 instance, either the default localhost or the
>named instance from another client.
>For example on my computer the other client can connect to the localhost and
>the other instance name such as server\instancenames cannot be connected. On
>the other computer that does not have the default instance, the client can
>only connect to one instance such as server\instancename.
>The error message is the same as when sql cannot connect.
named instance from another client.
For example on my computer the other client can connect to the localhost and
the other instance name such as server\instancenames cannot be connected. On
the other computer that does not have the default instance, the client can
only connect to one instance such as server\instancename.
The error message is the same as when sql cannot connect.
Mike
What version, edition of SQL Server? What is the exact error
message? What are you using to try to connect - application,
SQL Tools, DSN? Did you check for what instances are
running? The clients that can't connect to a named instance
- did you check their MDAC versions? Can you connect to
default and named instances when on the box where the
instances are running?
-Sue
On Thu, 23 Mar 2006 07:00:29 -0800, Mike9900
<Mike9900@.discussions.microsoft.com> wrote:
>We can only connect to only 1 instance, either the default localhost or the
>named instance from another client.
>For example on my computer the other client can connect to the localhost and
>the other instance name such as server\instancenames cannot be connected. On
>the other computer that does not have the default instance, the client can
>only connect to one instance such as server\instancename.
>The error message is the same as when sql cannot connect.
Can connect to only One instance from another computer
We can only connect to only 1 instance, either the default localhost or the
named instance from another client.
For example on my computer the other client can connect to the localhost and
the other instance name such as server\instancenames cannot be connected. On
the other computer that does not have the default instance, the client can
only connect to one instance such as server\instancename.
The error message is the same as when sql cannot connect.
MikeWhat version, edition of SQL Server? What is the exact error
message? What are you using to try to connect - application,
SQL Tools, DSN? Did you check for what instances are
running? The clients that can't connect to a named instance
- did you check their MDAC versions? Can you connect to
default and named instances when on the box where the
instances are running?
-Sue
On Thu, 23 Mar 2006 07:00:29 -0800, Mike9900
<Mike9900@.discussions.microsoft.com> wrote:
>We can only connect to only 1 instance, either the default localhost or the
>named instance from another client.
>For example on my computer the other client can connect to the localhost an
d
>the other instance name such as server\instancenames cannot be connected. O
n
>the other computer that does not have the default instance, the client can
>only connect to one instance such as server\instancename.
>The error message is the same as when sql cannot connect.
named instance from another client.
For example on my computer the other client can connect to the localhost and
the other instance name such as server\instancenames cannot be connected. On
the other computer that does not have the default instance, the client can
only connect to one instance such as server\instancename.
The error message is the same as when sql cannot connect.
MikeWhat version, edition of SQL Server? What is the exact error
message? What are you using to try to connect - application,
SQL Tools, DSN? Did you check for what instances are
running? The clients that can't connect to a named instance
- did you check their MDAC versions? Can you connect to
default and named instances when on the box where the
instances are running?
-Sue
On Thu, 23 Mar 2006 07:00:29 -0800, Mike9900
<Mike9900@.discussions.microsoft.com> wrote:
>We can only connect to only 1 instance, either the default localhost or the
>named instance from another client.
>For example on my computer the other client can connect to the localhost an
d
>the other instance name such as server\instancenames cannot be connected. O
n
>the other computer that does not have the default instance, the client can
>only connect to one instance such as server\instancename.
>The error message is the same as when sql cannot connect.
Subscribe to:
Posts (Atom)