Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts

Sunday, February 19, 2012

dbo owner

We are using SQL Express and I have a problem with dbo.

On my machine if I logon to SQL Express using windows authentication

and create a new database I automatically have db_owner role membership

on the new database.

On a colleagues machine, if he logs onto his SQL Express using windows authentication

and creates a new database he does NOT have db_owner role membership

on the new database.

How come?

I have checked pretty much everythng - windows built in admins, SQL express sysadmin roles

service pack versions but I can not find any difference in setup.

What should I do to his machine/SQL Express setup so he automatically has db_owner role membership

for every newly created database?

Thanks

Charlie

Hi, this sounds strange. The database creator should have db_owner role memebership by default. Which ower is assigned to the new database ? Is it dbo ? Is your Account you are using for the creation of the database part of the sysadmin role ? Then you probably already have dbo Owner rights through the group memerbership.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

I agree with Jens. This sounds strange, but most likely you get dbo access via sysadmin membership. I would first recommend trying the following query:

SELECT is_rolemember( 'db_owner' )

Members of db_owner as well as DBO should return 1 on the previous query.

I would also suggest trying the following query:

select name, type, usage from sys.login_token

order by type, usage, name

select name, type, usage from sys.user_token

order by type, usage, name

You should be able to see the login token as well as the user token on the current DB.

If the login token has an entry for sysadmin(sysadmin, SERVER ROLE, GRANT OR DENY) , then you should automatically be mapped to DBO on any DB. If you are not sysadmin, then pay attention to the user token.

Please let us know the results.

-Raul Garcia

SDE/T

SQL Server Engine

dbo access

Hi,
We have a sql 2000 machine that we use for our internal
intranet. It houses about 10 applications. Each db need
a user that an application can use. Is it advisable to
make those particular users dbo as they need privs to
create tables, sproc, views etc...
What is the best policy that other dba are using
ThanksPlease review this:
Microsoft SQL Server 2000 SP3 Security Features and Best Practices
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/default.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Friday, February 17, 2012

DBNMPNTW Access Denied Problem

Hi all

I have a program that accesses SQL 2000 that is running on a win2003 machine. The program works on my XP machine but does not work on my win98 machine, I have even opened up a port on the server so the database can be accessed externally (This seems to work fine as well, a friend of mine tested it for me).

The error message returned on the win98 machine is "[DBNMPNTW] Access Denied". Please help, thank you.

James :(I don't suppose you're on a domain are you? If not, try adding the win98 user computer\user to SQL Server as a user.|||Hi

I have managed to fix the problem. Yes i am on a domain, and my win98 machine can log onto AD (i installed AD client).

I simply added an extra field in my connection string and it worked, it's something to do with network, found it on the net somewhere.

James :)

Tuesday, February 14, 2012

Db-library network communications layer not loaded

I have an application that needs to to talk to MS SQL Server 2000.
When I connect from a client machine, I am getting db-library network
communications layer not loaded.
What component is it missing?
--
Cathy BIs the file Ntwdblib.dll in the system32 directory?
Ntwdblib is used for db-lib communications usually found in
older applications. It's not installed with MDAC.
-Sue
On Fri, 28 Jul 2006 07:43:02 -0700, Cathy Boehm
<CathyBoehm@.discussions.microsoft.com> wrote:

>I have an application that needs to to talk to MS SQL Server 2000.
>When I connect from a client machine, I am getting db-library network
>communications layer not loaded.
>What component is it missing?