Conference amcucs::ms-sqlsvr

Diane,

Go into enterprise manager, click on your server and choose edit using your
right-button. From there you can change the password for sa.

Regards,
Rudi

    That might work if I could register the server.  
    
    I gave up and de-installed SQL and then reinstalled.  That at least let
    me register the server again.
    
    Thanks
    Diane

    I'm now seeing the problem on a different server.  Here's what I did:
    
    Installed SQL6.0 
    Left the sa password blank.
    Backed up the master,tempdb etc databases.
    
    Try to upgrade SQL to 6.5.  Took the upgrade option.  It didn't ask for
    the sa password.  Rebooted server.  Now the services startup but I can
    nolonger make a SQL connection to the server.  I get login failed.  I'm
    using trusted connection which worked in 6.0.  I then tried using the
    standard security w/ sa and no password to connect.  I still get login
    failed.
    
    Any ideas why I'm having such a hard time upgrading?
    
    diane

    Hello,
    
    	RE .3,  When you Re-Installed SQL V6.0 did you switch your security
    settings from standard to Windows NT Integrated or Mixed? Then proceed
    to upgrade to SQL V6.5? If Yes, how did you set it up? Did you create
    a "Global Admins" group in the domain. Then create a "Local Admins"
    group on your SQL Server system. Then made the "Global Admins" a member
    of the "Local Admins" group?
    	Reason I'm asking is that Windows NT Integraded/Mixed security
    breaks from V6.0 to V6.5. Instead of making members part of the
    "Global" group, you have to add them all to the "Local" group. I
    couldn't get NT Integraded Security to work on V6.5. So in the
    Microsoft Knowledge base for SQL off of there homepage. I found out
    that its a bug.
    	I also remember reading somewhere that its not a good idea. To
    install SQL and leave the sa password blank. Always give sa a password.
    
    Ron

    1)When you Re-Installed SQL V6.0 did you switch your security
    settings from standard to Windows NT Integrated or Mixed?
    
    	I took the defaults when I did the install of SQL6.0.  I don't
    	remember it giving me a choice.  After the install of 6.0 when I
    	connected to the server I chose 'trusted' and was able to connect.
    	I didn't create any special groups or modified members.
    
    2)Instead of making members part of the "Global" group, you have to 
    add them all to the "Local" group.
    	
    	Being a novice to SQL are you talking about the NT user manager or
    	is there something in SQL I've should have done to the members
    	before I upgraded t 6.5.  I'm a little confused on this part.
    
    I'll change the sa password next time I install/re-install SQL.
    
    Thanks
    diane	

    
    	Hello,
    
    		Under V6.5, when you chose 'trusted' under Register Server.
    It assumes you have already set your security option in Server
    Configuration to be 'Windows NT Integrated' or 'Mixed'.
    	When I was talking about "Global" and "Local" groups. Yes, I was
    talking about NT User Manager. "Global" and "Local" groups help you
    manage security in SQL, if you are using 'Windows NT Integrated' or
    'Mixed' Security to manage your logins.
    	In your case your Security settings are set to 'Standard' and
    because you chose 'Trusted' Connection. SQL Enterprise Manager
    can't validate you as a 'Trusted' connection and won't let you login.
    	You would then assume okay, instead of 'Trusted', I'll switch it
    back to 'Standard' and manually type in the 'sa' and the password.
    Which is blank in your case. Which brings up another problem, V6.5
    mandates that passwords begin with a character, #, or underscore. So
    SQL Enterprise Manager won't let you login with a 'blank' sa password.
    So you are essentially locked out, I don't know how to by-pass this.
    Here is what I would do.
    
     Re-install V6.0 and change the sa password to something. Then when
    you go into Register Server. Leave the setting to 'Standard' and type
    in sa and the password. Enterprise Manager remembers the username and
    password, so you only have to type it in once. Then when you are ready,
    upgrade to V6.5. Once you are running V6.5, you can then start looking
    at 'SQL Security' and how it works with NT User Manager groups.
    
    
    Ron
    

    Thanks for the information.  However, it still didn't upgrade
    correctly.  Here's what I did:
    
    1) removed all signs/traces of SQL6.0 and 6.5
    2) Installed 6.0 and gave the SA a valid password.
    3) ensured that I was running "standard" security options
    4) upgrade to 6.5 (no problem)
    5) go to register the server under 6.5 and it complains about the sa
    password. I can no longer no login under sa and the password I used 
    with 6.0.  I was able to login under sa w/ the password no proble.
    
    I wonder if it's a problem with the Alpha version of SQL6.5 upgrade.
    Has anyone else tried an upgrade on an Alpha?
    
    thanks
    diane

    
    	Well, since I'm also a SQL novice, you got me stumped now. I
    upgraded to SQL V6.5 on an Alpha, without the problems you are seeing.
    
    Ron

    
    I have upgrade several Alphas from 6.0 to 6.5 with no difficulties.