nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

User Name Does Not Match User Schema

JoeBorgione

My new install of version 10 SQL Server SDE/Server is about to make me lose my mind.

In a sql server db (2008 r2)my user is the big kahuna I want to own everything, create feature classes etc. So, I go to this page in online help and create a schema that is owned by my user and named the same as my user.

However when I try to create a feature class in my database, I get the wretched User Name and User Schema Do Not Match error.

I'm going to step out and grab a tequila, so if you can provide even a hint as to what is going on with this, I'd really appreciate it!

タグ付けされた投稿をもっと見る

Accepted answers

All comments

JoeBorgione

So what you're *really* saying is that going out for a tequila ought to be in my vexatious
configuration toolkit, eh? I'll have to jot that one down...

- V

Absolutely! I'm thinking of working in a 'celebrate SDE' theme into my Cinco De Mayo bar-b-que....

😉

VinceAngelo

So what you're *really* saying is that going out for a tequila ought to be in my vexatious
configuration toolkit, eh? I'll have to jot that one down...

- V

KimPeter

Yeah, if they don't own data, they don't have to have a matching schema.

The only time that wouldn't be true is if you changed your ArcSDE log file configuration. If you didn't touch that (which most people don't as there is no need to), you should be fine.

JoeBorgione

Kim and Vince;

I think I just discovered the situation of my user and my user schema not matching; I just got back here and now my user can import, create, delete feature classes. The Network Guy fessed up that the domain controller had a little problem yesterday so my permissions weren't being passed through sde to sql; at least that's how he explained it.

That's what was driving me nuts; my user had all the right stuff including user mapping as suggested by Vince. See attached jpg. The data bases that kept tossing the error yesterday are shown as vecc430 and vecc2012; I have succesfully imported two feature classes into vecc2012 as user/schema vecc.

If I understand this correctly Kim: "If you have users who only edit data (they don't create data; some other user creates it and they just have rights to edit the data), those users don't have to have matching schemas. " you mean that my editors do not need a schema consistant with thier user names, correct?

I am about to test a few of my user logins for editing.

As always, thanks for the insight, advice, and above all, patience!

MyUserMapping.jpg

KimPeter

To be used with ArcGIS, all users who will create data in or import data to the geodatabase must have a schema name that matches its user name. Even though the database itself allows multiple users to write to one schema, ArcGIS can't work with that. That is true no matter what your underlying database version is.

If you have users who only edit data (they don't create data; some other user creates it and they just have rights to edit the data), those users don't have to have matching schemas. Same thing for read-only users. You just have to be careful that you don't later grant those users the privileges necessary to create data...at that time, their data creation efforts will fail because the schema names don't match the user names.

Hope this helps.

Kim

JoeBorgione

V & K-

Big kahuna is just my term for the user that has the most rights; I actually use a one word user name, and all my subordinate users are one word as well.. (Sorry, an attempt at humor to hide my overwhelming frustration...)

Inititially my default schema was dbo; isn't that the default if you don't specify one? So I should check the user mapping and make sure it goes to my default schema instead of dbo? Or....

Perhaps either of you can answer another question about schemas: I created one, owned by my user, that has the dataset permissions shown as 'Data Editor' in the link provided above for my other users. I set each of them up with this schema as the default; it's called (drum roll) userschema. Somewhere in my seemingly endless googling it was mentioned that users and their schemas need to have the same name; I think that was sql server 2005 though. To me that flies in the face of having multiple users having the same default schema, right? So the question is, should all of my (editor) users have their own personalized schema? (Ugggh; seems like a lot of redundant work and I only have a dozen or so users)... Or should they just have a public schema and I take care of their permissions in a role like I did in sql server 2000?

Thanks-

KimPeter

Joe,

Can you post a copy of the SQL used to create the database user and schema? (You can leave out the password text.)

Is the actual name "big kahuna" with a space? Database principals and securables usually shouldn't have spaces in them, so maybe that's messing up things? I tried to find in Microsoft's doc if they say whether or not you can include spaces. I couldn't find an explicit statement, but none of their examples show users or schemas with spaces in them.

-Kim

VinceAngelo

Is your big kahuna a local administrator? Microsoft does us the favor of mapping all
administrators to dbo.

- V

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.