I forgot my SA password for my instance of SQL 2000

Hi all,

I have SQL 2000 and I forgot my SA password and cannot login as administrator using windows authentication.

Is there any way to reset SA password?

"Mixed Mode" authentication is enabled.

If I change authentication mode in register to Windows only and then after restarting SQL change it back to Mixed, will it reset SA password to "null"?

Thanks in advance.

If you log onto the machine with the Database server installed and use the local administrator account or a network administrator account you should be able to reset the password.

|||Just in addition to Glenns post and your qustion: It won′t reset the password to null with changing the authentication type back and forth. If you don′t have any GUI to administer your passwords you can use the procedure sp_password passing in a NULL for the old password parameter, as you don′t need the old if you are logged on as a user with sysadmin / securityadmin rights.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||As I said before I can't login even with local Administrator. I don't know what is going on. It is so weird.

I forgot my SA password for my instance of SQL 2000

Hi all,

I have SQL 2000 and I forgot my SA password and cannot login as administrator using windows authentication.

Is there any way to reset SA password?

"Mixed Mode" authentication is enabled.

If I change authentication mode in register to Windows only and then after restarting SQL change it back to Mixed, will it reset SA password to "null"?

Thanks in advance.

If you log onto the machine with the Database server installed and use the local administrator account or a network administrator account you should be able to reset the password.

|||Just in addition to Glenns post and your qustion: It won′t reset the password to null with changing the authentication type back and forth. If you don′t have any GUI to administer your passwords you can use the procedure sp_password passing in a NULL for the old password parameter, as you don′t need the old if you are logged on as a user with sysadmin / securityadmin rights.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||As I said before I can't login even with local Administrator. I don't know what is going on. It is so weird.|||

Try

sp_password NULL,NULL,'sa'

Assuming you never created password at the first place. parameter 1 is Old password, parameters 2 is new password, parameter 3 is user.

I can no longer connect to my SQL Server Express 2005 from Manager Studio Express

Everything was working fine. I have been able to connect using windows authentication. Then, I went into the ODBC manager to add a data source and it failed to connect so I went back into the Server management studio to modify users. After doing this I now get an error when I try to conenct the management studio to the SQL server.

I wasn't modifying the login for my windows account that I normally use, I was modifying a different one, however I now get the message "An error has occured while establishing a connection to the SQL server. This kind of problem can ocure because the default behavior of the server does not support all connection methods" blah blah.

Does anyone know how I can attach to the server? Or, do I need to somehow remove the server and create a new one? How would I do that?

Thanks in advance for any input.

Hi,

did you disable remote connections by accident ? If so, see if this feature is enabled under the Serface Configuration. See more detaisl on the screencast on my site.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

I am accessing data using data access pages in IIS 7 to SQL server 2005 Authentication is failin

is there a step by step paper to get there? here is what i need to consider. I Iwill have many customers that will need their own set of records and access pages "branded for their company" each customer will have many clients. I am hosting this application on a windows 2003 server with SQL 2005 server enterprise.

I am using windows authentication, I have created a username in windows, then i added the windows user in SQL management studio in security, granted "DB Read" and "DB write" and again under the database security tab. still from the web authentication fails. i must be nissing a step or two?

I expect to set up a username for each database as i setup new customers.

There is another post that had a similar issue...the discussion there may prove to be relevant for you:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=978330&SiteID=1

The important step is to disable Anonymous Authentication on your web server and enable Integrated Windows authentication. This will get the database request running in the context of the user making the web request (as opposed to the context of the default anonymous account).

Note that for data security/privacy reasons, you will probably want to avoid having clients from different companies, etc. sharing the same database and/or tables.

I am accessing data using data access pages in IIS 7 to SQL server 2005 Authentication is fa

is there a step by step paper to get there? here is what i need to consider. I Iwill have many customers that will need their own set of records and access pages "branded for their company" each customer will have many clients. I am hosting this application on a windows 2003 server with SQL 2005 server enterprise.

I am using windows authentication, I have created a username in windows, then i added the windows user in SQL management studio in security, granted "DB Read" and "DB write" and again under the database security tab. still from the web authentication fails. i must be nissing a step or two?

I expect to set up a username for each database as i setup new customers.

There is another post that had a similar issue...the discussion there may prove to be relevant for you:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=978330&SiteID=1

The important step is to disable Anonymous Authentication on your web server and enable Integrated Windows authentication. This will get the database request running in the context of the user making the web request (as opposed to the context of the default anonymous account).

Note that for data security/privacy reasons, you will probably want to avoid having clients from different companies, etc. sharing the same database and/or tables.