userprincipalname vs samaccountname in LoginType.WindowsUser

Question

Hello,

we are using the Microsoft.SqlServer.Management.Smo framework in an .net application to provision windows users in our SQL 2008 database. However, only logins in the old domain\username (=samaccountname) form were accepted in the code. 

We start upgrading to SQLserver 2012 soon, and the provisioning scripts have to be updated. Is the [e-mail] (userprincipalname) supported in the newest (2012) version of this library?

Login lgn = new Login(srv, dbUser); //only works if dbUser is in the form domain\username
lgn.DefaultDatabase = db.Name;
lgn.LoginType = LoginType.WindowsUser;
lgn.Create();

---

gradnet

Answer 1

Hi gradnet,

According to backwards compatibility of SQL Server product, what you mentioned is supported in the SQL Server 2012.

---

Best Regards,
Peja

Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Answer 2

I installed mssql 2012 to figure out the answer to this question. The result was rather disappointing: upn's are not supported in mssql 2012. 

because we use structured and long usernames in our domain, the resulting SAMaccountnames are automatically generated by AD. 

This implicates we will have to manage users with names like domain\$0O9100-OHDDC94LEOBC

---

gradnet