It really depends on the enviornment the sql server will be going in.
In development envos, it really does not matter a great deal unless you do not want other developers to be able to see what you are working with. If working with information that is senseative(sp), then change it.
For testing or development, change it.
I always change it out of habit. If security is not a worry, have all of them set to the same password, just not blank.
If you don't, you leave your entire network at risk - not just SQL Server. Do you wonder why the latest SQL Server Worm spread so quickly and infected 1000's of servers in a couple of days? Those servers did not have an SA password. The worm took advantage of that.
Please read the following threads and the links in the threads to get an idea about how much more seriously SQL DBAs and developers need to be regarding security. This is not just about data confidentiality. It is about having a network that functions properly as well.
thread183-280043
thread183-279012 Terry L. Broadbent - DBA
Computing Links:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.