Skip to main content

SSMS 2008 and changing a SQL 2005 SA password.

You can probably tell from some of my more recent posts that I have been doing some work lately on SQL Server 2008. I have also recently (the last two months) upgraded my work desktop to Windows 7. As a result of this of this, and the continued migration away from SQL Server 2000 I have only installed the SQL Server 2008 client tools (Management Studio) onto my desktop and I use that for working on both SQL Server 2005 and SQL Server 2008 instances.

This week, for reasons beyond the scope of this post I wanted and needed to change the sa password on one of my SQL Server 2005 instances. No problem I thought, I already had SSMS 2008 open on my desktop. I connected to the SQL Server 2005 instance using Windows Authentication. (The SA account is not generally used) I opened the security folder, and then the logins folder, right-clicked on the sa login and selected properties. The properties box opened, I typed a new 'password' into the 'password and confirm password' dialogue box and clicked <OK>. To my shock and horror I got the following error:

Cannot set a credential for principal 'sa'. (Microsoft SQL Server, Error: 15535)

Well that surprised me, if it didn't surprise you. I tried to login using the old SA password and it logged in fine. I then realised that it must be related to changing the sa password of a SQL Server 2005 instance using SSMS 2008.

Well I cheated and remote connected to the server hosting the 2005 instance, and used the SSMS 2005 installed on there. I needed to change the password quickly but I wanted to figure out what had prevented me changing the password in SSMS 2008.

Returning to my test domain later in the day, I was able to recreate the problem again, simply by trying to change the sa password of a 2005 instance using SQL Server 2008 Management Studio. I went to search the web and found this:

The solution is very simple, the "map to credentials" check box in the properties Window is not selected. The above article explains why this is the case. Tick the box and change the password and all is well.


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…