Oops - you used the "S-word"! The article is for MS SQL2000 (I have 2005), and it says to launch the Enterprise Manager. However, that app (if it is still in 2005) is not in an obvious location. It has no Start menu icon.
I would imagine it is part of the "Management Studio", which can apparently be run only by "sa". FWIW, I have determined that the local administrators do have access to the database itself. The system of which it is a part does produce reports from it. Our developers, when using a 3rd party tool (AQT), can run the tool (remotely) as the administrator of the SQL server and make an ODBC connection to the tables. It's just the Management tools which are unavailable (necessary for using the backup tools, creating a "read only" user account for making custom reports, etc.) -------------------------------------- Richard McClary, Systems Administrator ASPCA Knowledge Management 1717 S Philo Rd, Ste 36, Urbana, IL 61802 217-337-9761 http://www.aspca.org "Michael B. Smith" <[email protected]> wrote on 02/10/2009 03:31:14 PM: > I'm not a sql guru, although I played one in a former job for a short period > of time. > > You can reset the 'sa' password, but it's a "non-trivial operation". > > Generally, if SQL is installed in a domain environment, then domain admins > also have sysadmin privileges. If a workstation environment, then the > builtin\administrators group. > > So....if the defaults were used, this should work: > > http://www.mssqlcity.com/FAQ/Admin/forgot_sa_password.htm > > Regards, > > Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP > My blog: http://TheEssentialExchange.com/blogs/michael > I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Tuesday, February 10, 2009 4:21 PM > To: NT System Admin Issues > Subject: Cracking into MS SQL2005 > > Greetings! > > As a part of a "system", a MS SQL-2005 server was set up. Now it seems > the guy who installed it ran away with the password for the SA account. > > Another person from that company set up another SQL admin account (said > "SA" couldn't be re-set). However, when I try to open the Management > Studio, I get this Error 233: > > "A connection was successfully established with the server, but then an > error occurred during the login process. (provider: Shared Memory > Provider, error: 0 - No process is on the other end of the > pipe.)(Microsoft SQL Server, Error: 233)" > > So, does this mean the account created is not a DBA on this system (it is > a local admin), or that only "sa" has access to the Managemen Suite, or > that something is broken and the account ought to be able to open the > management suite, or ???? > > (To aggrivate things, none of us here are MS-SQL folks. Plenty of IBM > DB2, MySQL, etc, but no MS-SQL.) > -------------------------------------- > Richard McClary, Systems Administrator > ASPCA Knowledge Management > 1717 S Philo Rd, Ste 36, Urbana, IL 61802 > 217-337-9761 > http://www.aspca.org > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
