We all have times when we’re not sure we know what to do. It’s those times when we don’t know what to say or how to act.
We all have times when we are unsure of our ability to make a good first impression at a party. But that feeling of uncertainty doesn’t always have to lead to disaster. A lot of the time we are not even sure if we can do something.
Well today I got a chance to talk to a SQL server specialist for a few minutes, and that was the result of all of my hesitation. With some of them I can certainly agree that you need to be sure you are prepared, but not all of them think you should go down the path of giving a complete stranger your password. To this day I still remember how I felt like the first time I gave my mother my password.
My mother was a very easygoing lady. My first experience with someone trying to access my database was by her using the password I had given my friend, and my friend immediately changed the password. I was so scared that I was going to lose all my stuff. But then my mother started talking to me about her experience. She said that she had given her friend the same password she had given me.
I don’t know that you’re right about getting this computer from a bad guy, but in this case you may be correct. I can’t imagine she would have been able to connect with a password that was her own, and her friend would have been able to get to her. So that was the way it went. I’m not sure how she learned to get the password, but I think she got her password on the computer that way.
This is a good time to talk about something that’s been a major issue with SQL Server authentication. If you’re going to take the time to look up your own password, you should do it from a Microsoft account. The Microsoft account is locked, and can only be unlocked by a registered Microsoft account. This means that if your friend did have a Microsoft account, she would have to do all of that work to get access to this computer.
In SQL Server 2008, there is a new password policy that makes it much, much easier to get your account password. Previously, if you were using a Windows account, your account password had to be sent to the account you were logging in from. The new password policy, however, allows you to type in your password right from your own account.
In my case, my account password is my name and that’s it. However, I have had to change this password on a few occasions, and it has been a pain in the ass. If you are having trouble, there are some tips on how to reset your password.
The new SQL Server account password is also stored in the user profile table (which is the same as the account password). To change the password, go to Users, right click on your user name, and select Properties. In the Security tab, click on the Change Password link. Enter a new password as needed.
I don’t know this one, but it’s about as good as it gets. If I change the password twice, will it work? Or will it keep going for a few more seconds and then fail? This is how I want the system to function. I am using the latest version of SQL Server, and if I can change it back to the default one, there is a chance this would work.