This is the one that gets me upset most of the time:
quote:
The only problem here can be third party software that utilises SQL Server as its security or other repository in order to run. I have come across a few products that prompt to for the SA password, then end up creating a database with no other user but SA, only to spend hours reading documentation and testing to change it.
Certain products balk at when they run in anything less than dbo and when making the ODBC connections, you have the same username and password. This leaves a database wide open and just causes headaches. Grrr.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley