deleted AD

I am not a DBA and may have a problem. I am running an
app that sits on top of the sql desktop engine. I am
using AD integrated security. My problem is that one of
the domain admins decided to reformat and reinstall both
our AD servers.(#$%#) There is a new domain, but there is
no longer an AD server for the account that "owns" the
sql database.
I am still logged in to the server with the account that
owns the database. I have not logged out since the AD was
deleted for fear that my database will no longer be
accessible. As far as I can see, the admin tools
available to me for the desktop engine don't have the
ability to change the owner of the database.
What must I do to ensure that I can access this database?You can change the database owner with sp_changedbowner. Run this using the
command-line OSQL utility like the example below:
OSQL -Q "EXEC sp_changedbowner 'sa'" -d MyDatabase -E -S MyServer
By default, members of the local Administrators have sysadmin access to SQL
Server via the 'BULTIN\Administrators' login. This will provide sysadmin
access to your SQL Server instance as long as you can access the machine
with Windows account that is a member of the local Administrators group.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"hhtpnoc" <anonymous@.discussions.microsoft.com> wrote in message
news:413301c3e42f$29ac0100$a301280a@.phx.gbl...
> I am not a DBA and may have a problem. I am running an
> app that sits on top of the sql desktop engine. I am
> using AD integrated security. My problem is that one of
> the domain admins decided to reformat and reinstall both
> our AD servers.(#$%#) There is a new domain, but there is
> no longer an AD server for the account that "owns" the
> sql database.
> I am still logged in to the server with the account that
> owns the database. I have not logged out since the AD was
> deleted for fear that my database will no longer be
> accessible. As far as I can see, the admin tools
> available to me for the desktop engine don't have the
> ability to change the owner of the database.
> What must I do to ensure that I can access this database?
>

deleted AD

I am not a DBA and may have a problem. I am running an
app that sits on top of the sql desktop engine. I am
using AD integrated security. My problem is that one of
the domain admins decided to reformat and reinstall both
our AD servers.(#$%#) There is a new domain, but there is
no longer an AD server for the account that "owns" the
sql database.
I am still logged in to the server with the account that
owns the database. I have not logged out since the AD was
deleted for fear that my database will no longer be
accessible. As far as I can see, the admin tools
available to me for the desktop engine don't have the
ability to change the owner of the database.
What must I do to ensure that I can access this database?You can change the database owner with sp_changedbowner. Run this using the
command-line OSQL utility like the example below:
OSQL -Q "EXEC sp_changedbowner 'sa'" -d MyDatabase -E -S MyServer
By default, members of the local Administrators have sysadmin access to SQL
Server via the 'BULTIN\Administrators' login. This will provide sysadmin
access to your SQL Server instance as long as you can access the machine
with Windows account that is a member of the local Administrators group.
Hope this helps.
Dan Guzman
SQL Server MVP
"hhtpnoc" <anonymous@.discussions.microsoft.com> wrote in message
news:413301c3e42f$29ac0100$a301280a@.phx.gbl...

quote:

---

> I am not a DBA and may have a problem. I am running an
> app that sits on top of the sql desktop engine. I am
> using AD integrated security. My problem is that one of
> the domain admins decided to reformat and reinstall both
> our AD servers.(#$%#) There is a new domain, but there is
> no longer an AD server for the account that "owns" the
> sql database.
> I am still logged in to the server with the account that
> owns the database. I have not logged out since the AD was
> deleted for fear that my database will no longer be
> accessible. As far as I can see, the admin tools
> available to me for the desktop engine don't have the
> ability to change the owner of the database.
> What must I do to ensure that I can access this database?
>

---

Delete Update Behavior of the SSEv Engine

Can someone on the team tell me if a delete or update orphans a row in the SQL Server Everywhere database that must be compacted out to free the space? I understand that Compact runs automatically when the last connection is closed but does this create another copy of the database as it does with JET or is this an update-in-place. Is this an opportunity to corrupt the database if the process is interrupted by power-failure or a truck running over the device from right-to-left?

Hmm..I think there is some misunderstanding here. When the last connection to database is closed COMPAT IS NOT RUN automatically. There is a similar thing called 'Auto Shrink' that runs if the space available (and sparse) is more than a threshold. COMPACT need to be run explicitly. When you run COMPACT, you can specify the destination database. The destination database can also be same as the source database file. In any case, the compaction first happens into a temp database file, the original file deleted, the temp files gets renamed.

Thanks,

Laxmi

Delete Update Behavior of the SSEv Engine

Can someone on the team tell me if a delete or update orphans a row in the SQL Server Everywhere database that must be compacted out to free the space? I understand that Compact runs automatically when the last connection is closed but does this create another copy of the database as it does with JET or is this an update-in-place. Is this an opportunity to corrupt the database if the process is interrupted by power-failure or a truck running over the device from right-to-left?

Hmm..I think there is some misunderstanding here. When the last connection to database is closed COMPAT IS NOT RUN automatically. There is a similar thing called 'Auto Shrink' that runs if the space available (and sparse) is more than a threshold. COMPACT need to be run explicitly. When you run COMPACT, you can specify the destination database. The destination database can also be same as the source database file. In any case, the compaction first happens into a temp database file, the original file deleted, the temp files gets renamed.

Thanks,

Laxmi