Hi, I have a customer that is planning on moving to new hardware and performing a SQL upgrade (2000->2005). I know that our application (FileNet Image Services) is sensitive to what we refer to as an "orphaned" database. Our app stops working if a database is simply detached/attached to another server because it loses that link between the users in the database and the users in SQL Security. Once that happens, that users cannot simply be recreated in Security-Logins. Because of internal IDs the users no longer match and our app stops working.
Any ideas to get around this?
SQL2000 to SQL2005 migration/upgrade need to preserve user security
June 16, 2010 2:24 PM
December 7, 2013 12:49 AM