Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How should I convert logins afer a SQL Server 2005 upgrade?

April 26, 2017afer convert logins SQL Server upgrade

0

Posted

How should I convert logins afer a SQL Server 2005 upgrade?

1 Answer

0

Posted

In SQL Server 7 and 2000, when you create an object owned by a user other than DBO, you have to qualify the object by owner name when accessing it, unless you are logged in as that user. In SQL Server 2005, objects are no longer qualified by owner. Instead, they’re qualified by schema name. This is something I covered in a recent SearchSQLServer.com tip on SQL Server 2005 permissions. In essence, this will result in less confusion regarding object qualification; you will be able to organize objects logically, rather than by who owns them. As for server logins, I don’t see a lot of potential issues. The same semantics apply in terms of what logins are to SQL Server and how they work. One difference you might want to be aware of is SQL Server 2005’s ability to enforce password policies, which may mean that some of your users will have to change their passwords after your upgrade. Adam Machanic, SQL Server 2005 Expert Return to SQL login and permissions FAQs 5.