Recovering SA Password or Adding sysadmin Login

Hi,
Recently some body played with our SQL Server and removed our Sys admin
group login and we dont have builtin\admin as login and no SA Password
can any body tell the way to come out with this situation to change the SA
Password or create our Group back with Sys admin priviledges.
also to confirm we are still in NT admin group for the server.
below article talk about similar case but as soon as i try to run sqlcmd
utility after taking server in single mode as per article ,it throws error
that you cant run sqlcmd since server in Single user mode.
Any help is appreciated..."sacgar" wrote:
> Hi,
> Recently some body played with our SQL Server and removed our Sys admin
> group login and we dont have builtin\admin as login and no SA Password
> can any body tell the way to come out with this situation to change the SA
> Password or create our Group back with Sys admin priviledges.
> also to confirm we are still in NT admin group for the server.
> below article talk about similar case but as soon as i try to run sqlcmd
> utility after taking server in single mode as per article ,it throws error
> that you cant run sqlcmd since server in Single user mode.
> Any help is appreciated...
Adding Link
http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx

Recovering SA Password or Adding sysadmin Login

Hi,
Recently some body played with our SQL Server and removed our Sys admin
group login and we dont have builtin\admin as login and no SA Password
can any body tell the way to come out with this situation to change the SA
Password or create our Group back with Sys admin priviledges.
also to confirm we are still in NT admin group for the server.
below article talk about similar case but as soon as i try to run sqlcmd
utility after taking server in single mode as per article ,it throws error
that you cant run sqlcmd since server in Single user mode.
Any help is appreciated...
"sacgar" wrote:

> Hi,
> Recently some body played with our SQL Server and removed our Sys admin
> group login and we dont have builtin\admin as login and no SA Password
> can any body tell the way to come out with this situation to change the SA
> Password or create our Group back with Sys admin priviledges.
> also to confirm we are still in NT admin group for the server.
> below article talk about similar case but as soon as i try to run sqlcmd
> utility after taking server in single mode as per article ,it throws error
> that you cant run sqlcmd since server in Single user mode.
> Any help is appreciated...
Adding Link
http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx

Records don't lock-one user receives error

I created a MSAccess application with the forms in one db (front end) and the tables in another db (back end). The network admin migrated the back end to SQL Server. With a few minor changes (changing -1 to 1 in queries, etc.) the migration seemed to go pretty smoothly and everything works fine except....

The MSAccess backend used to lock records when someone was editing them. The status of the record was indicated in the record selector on each form, a right pointing arrow to indicate the record was free, a pencil with three dots indicating the record was locked by the current user, and a circle with a diagonal line to indicate the record was locked by another user. When 2 users attempted to simultaneously edit a record, the first user got the lock on the record. The second user received a message as soon as they attempted to edit the locked record to the effect that the record was locked.

Now (since the migration to SQL Server) the record selectors no longer give any indication as to the locking status of the records. When 2 users attempt to simultaneously edit a record, both are able to enter information in their forms, but when the second user attempts to save the record they receive the following message:

This record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes the other user made. Copying the changes to the clipboard will let you look at the values the other user entered, and then paste your changes back in if you decide to make changes.

Please help me find the cause of this behavior. Is it something I need to change in the MSAccess front end or something that needs to be set in the SQL Server back end by the network admin?

I am moving this question to the SQL Server Database Engine forum.