Hi,
We have a legacy app that was originally built on site but, of course, the source code disappeared long ago. Well wouldn't you know it but the sa username and password is hard coded into that app and it isn't very "strong". The SQL database is isolated however, so we aren't too worried about the mixed mode security.
We want to upgrade to SQL 2005 but we weren't able to use the old sa password. Is there a way, probably post installation, to force the sa password to be the one we need to get the legacy app to work?
Thanks!
We have a legacy app that was originally built on site but, of course, the source code disappeared long ago. Well wouldn't you know it but the sa username and password is hard coded into that app and it isn't very "strong". The SQL database is isolated however, so we aren't too worried about the mixed mode security.
We want to upgrade to SQL 2005 but we weren't able to use the old sa password. Is there a way, probably post installation, to force the sa password to be the one we need to get the legacy app to work?
Thanks!