santacatalin.info

Even if the SQL instance is using Windows authentication, you must provide a strong password. We know that while using Windows authentication, the SA account is not used by any user. But the current instance can later be switched to Mixed Mode, and then the SA account becomes an active login. Therefore, it is suggested that you should not assign the password blank or NULL. It should have strong encryption.

If the SA (SQL authentication login) account has a null, blank, simple, or well-known password, when an instance of MSDE 2000 is switched to Mixed Mode, the MSDE instance can then be easily accessed by unauthorized users. The SA account cannot be dropped, and it must always be protected with a strong password to help restrict unauthorized access. Any user who gains access to an instance of MSDE 2000 indirectly get full control on that instance of MSDE, and have the ability to access any resources that the MSDE service account has.

To avoid such circumstances, you can use custom application code to install MSDE or SQL Server Desktop Engine. For that observe the given points.

*

If the user is going to set up MSDE in Mixed Mode, and is going to use the SA account, request a strong password for the SA account from the user. Use that password in the MSDE setup.
*

If the SA account is not used, generate a random string, and then pass that string as the SA password to the MSDE setup.

If somehow you forget the SQL server database password or you have lost the SQL server database .MDF password, you need to recover the SQL Server password immediately. What should be your course of action to deal with such awkward situation where you don’t want to compromise with the security of SQL database?

Using SQL Server password recovery software will help you in recovering lost/forgotten passwords of master data file .MDF of SQL server database. Even the multilingual passwords are recovered instantly with the help of software. skorea.