Here is my next question.. I am told to completely get rid of sa login as
multiple users know the password. Instead of just changing the password, I
am told that it is a good practice that we don't have sa at all (from my
training class). I created a new login with all privileges that sa had.
Now, as a DBA, only I know the password to this login.
Now, I was verifying all the databases and jobs and alerts and objects owned
by sa. I see that almost all the databases and jobs are owned by sa. When
I looked up sp_changedbowner in BOL, it tells me that I can't change the
owner of system databases. So I guess, I can't drop sa. Has anyone run into
this situation before? I don't understand why the Microsoft certified
trainer said that I should drop sa login as soon as possible when system
databases are owned by sa during SQL installation. I am confused. Can
anyone help me???