Eric Barro
ebarro at afsweb.com
Mon Oct 11 23:43:56 CDT 2004
John, Here's a stab in the dark... Check to see what Windows account SQL server and SQL server agent is running on for each machine. By default it assumes that you will be running it under the Administrator account for that machine unless you change it. If it is running under a different account then you will need to make sure that the account it is running in has the correct rights and privileges for SQL server to function properly. By default the Administrators group is included as a login in SQL server. It is called BUILTIN/Administrators when you look in the Security section (Login) in EM. I'm guessing that part of your problem stems from the fact that you don't have synchronized accounts on all the machines. If you ensure that all the Administrator logins in all your Windows machines that are running SQL server are the same then you should technically have no problems. If you are using a different account to run SQL server you will need to make sure that you are using the same account on all machines and that account has the same rights and privileges to run SQL server. Bottom line is...synchronize all the accounts that run SQL server on all machines. -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Monday, October 11, 2004 9:02 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Problems registering database Well, I spoke too soon. Now Neo2 is pegging the CPU usage all the time, and EM can't even get in to it's own database (local). Or more correctly it can see the db but when I try and click on databases it just hangs with the hourglass. Which is a catastrophe! Before I could at least use Neo2 from Neo2, now I can't do anything at all. Come to think of it, it may be trying in vain to roll back a transaction or something. I had QA running an update query when I changed the login type property which forcefully shut down SQL Server. I think I'll go to bed and pray that this thing survives. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of John W. Colby Sent: Monday, October 11, 2004 11:43 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Problems registering database Andrew, Well, halafrigginlula. On Soltek1 I tried to register Neo1 and Neo2, using sa and the password. Neo2 registered correctly, Neo1 gives me a "login failed for user sa". Likewise, on Neo1 I registered Neo2 using sa and the password. Soltek1 was already registered. My laptop ColbyM6805 registered Neo2 using sa and the password but the registration of Neo1 and Soltek failed. From my wife's machine MaryDesktop I can see all the other servers but only Neo2 registered successfully. Neo1 and Soltek1 failed with the "login failed for user sa" and M6805 failed with the infamous "guest". In fact this gets me 1/2 way there since the nVLDB physically resides on Neo2, I can now bang at it from Neo1, Soltek1, MaryDesktop and my Laptop. I am definitely thrilled at the improvement in my situation however I'm also very uneasy that I have no clue why this "X registers but Y fails" is going on. I also tried to use the property dialog of the local laptop on my laptop to set the startup service to sa and oh man what a mistake THAT was. Now I can't get the local database to login at all. It tells me the login is broken or something (so true! 8( I can't get at the property dialog, I can't start the service manager, basically I am really hosed on that machine. Which is a problem since a database for a project I am working on is on that machine. Sigh. So any ideas how do I get back in to this database? Any ideas why the sa account works on Neo2 but not on Neo1 or Soltek1? Is there any way to just look at all the accounts like you can in Windows? If I could do that I might be able to compare machine to machine and see what the heck is going on here. AFAIK I just told it the default install of SQL Server so I just don't understand why the responses are so different from machine to machine. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Haslett, Andrew Sent: Monday, October 11, 2004 10:45 PM To: 'dba-sqlserver at databaseadvisors.com' Subject: RE: [dba-SQLServer] Problems registering database You did it all correctly except the account isn't 'administrator', its actually just 'sa' (which stands for system administrator). So the username is actually sa and the password is what you specified. The security risks you speak of are correct, as the sa account has full rights over the entire instance of SQL Server you are using, which you often don't require - however if you were to use Windows Auth, you'd still need to set up the login and access permissions for *an* account in SQL itself for it to work. Therefore whichever way you go, you'd still have to learn about logins / roles / security etc. and from what I understand of your requirements, you don't have time to learn or master this. Therefore, the sa account is the easiest for you to setup and use, as it will require no configuration of account / security etc -> and as (I think) you're on a (relatively) isolated network with hardware, software firewall / NAT etc., the security risks are no more severe than if someone hacked into your machine anyway. Cheers, A _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com ----------------------------------------- The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication.