Power Failure for SQL Server 2000

We encounter a power failure for about half an hour and
the SQL Server 2000 is back again.
For production databases, we use FULL Recovery Model with
Transaction Log backed up every half an hour. After power
is up, everything works properly.
I would like to know what happens to the SQL Server 2000
when the power fails and how the data is recovered when
power is up again.
ThanksRegardless of the recovery model, each database is automatically recovered
when the instance starts. Data are read from the transaction log since the
last checkpoint and applied to the database. Uncommitted transactions are
then rolled back. The end result is that the database is recovered to the
point of the failure, less uncommitted transactions.
Your FULL recovery model and log backups provide extra protection in the
event of media loss due to hardware failure or data corruption.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
> We encounter a power failure for about half an hour and
> the SQL Server 2000 is back again.
> For production databases, we use FULL Recovery Model with
> Transaction Log backed up every half an hour. After power
> is up, everything works properly.
> I would like to know what happens to the SQL Server 2000
> when the power fails and how the data is recovered when
> power is up again.
> Thanks|||Dear Dan,
Thank you for your advice.
However, for SIMPLE Recovery Model, there will be no
transaction log backup. To what state does the database
recovered to ?
Besides, would you mind to elaborate on the extra benefit
of using FULL Recovery Model ?
Thanks again.
>--Original Message--
>Regardless of the recovery model, each database is
automatically recovered
>when the instance starts. Data are read from the
transaction log since the
>last checkpoint and applied to the database. Uncommitted
transactions are
>then rolled back. The end result is that the database is
recovered to the
>point of the failure, less uncommitted transactions.
>Your FULL recovery model and log backups provide extra
protection in the
>event of media loss due to hardware failure or data
corruption.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Peter" <anonymous@.discussions.microsoft.com> wrote in
message
>news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
>> We encounter a power failure for about half an hour and
>> the SQL Server 2000 is back again.
>> For production databases, we use FULL Recovery Model
with
>> Transaction Log backed up every half an hour. After
power
>> is up, everything works properly.
>> I would like to know what happens to the SQL Server 2000
>> when the power fails and how the data is recovered when
>> power is up again.
>> Thanks
>
>.
>|||Peter
<http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1
> --administaiting best practices
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
> >--Original Message--
> >Regardless of the recovery model, each database is
> automatically recovered
> >when the instance starts. Data are read from the
> transaction log since the
> >last checkpoint and applied to the database. Uncommitted
> transactions are
> >then rolled back. The end result is that the database is
> recovered to the
> >point of the failure, less uncommitted transactions.
> >
> >Your FULL recovery model and log backups provide extra
> protection in the
> >event of media loss due to hardware failure or data
> corruption.
> >
> >--
> >Hope this helps.
> >
> >Dan Guzman
> >SQL Server MVP
> >
> >"Peter" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
> >> We encounter a power failure for about half an hour and
> >> the SQL Server 2000 is back again.
> >>
> >> For production databases, we use FULL Recovery Model
> with
> >> Transaction Log backed up every half an hour. After
> power
> >> is up, everything works properly.
> >>
> >> I would like to know what happens to the SQL Server 2000
> >> when the power fails and how the data is recovered when
> >> power is up again.
> >>
> >> Thanks
> >
> >
> >.
> >|||Automatic recovery (what happens when you start SQL Server) doesn't have anything to do with
backups. SQL Server records all modifications in the transaction log, regardless of recovery model.
In simple, SQL Server removes log records from the transaction log when they aren't needed anymore
for this automatic recovery.
Full recovery model allow you to backup transaction log. This has a lot of advantages, like backup
log even of the database becomes corrupt, point in time restore etc.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
>>--Original Message--
>>Regardless of the recovery model, each database is
> automatically recovered
>>when the instance starts. Data are read from the
> transaction log since the
>>last checkpoint and applied to the database. Uncommitted
> transactions are
>>then rolled back. The end result is that the database is
> recovered to the
>>point of the failure, less uncommitted transactions.
>>Your FULL recovery model and log backups provide extra
> protection in the
>>event of media loss due to hardware failure or data
> corruption.
>>--
>>Hope this helps.
>>Dan Guzman
>>SQL Server MVP
>>"Peter" <anonymous@.discussions.microsoft.com> wrote in
> message
>>news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
>> We encounter a power failure for about half an hour and
>> the SQL Server 2000 is back again.
>> For production databases, we use FULL Recovery Model
> with
>> Transaction Log backed up every half an hour. After
> power
>> is up, everything works properly.
>> I would like to know what happens to the SQL Server 2000
>> when the power fails and how the data is recovered when
>> power is up again.
>> Thanks
>>
>>.|||To add to the other responses, automatic recovery will recover databases to
the same consistent state regardless of the recovery model.
Separately, database and transaction log backups reduce your vulnerability
to potential data loss. For example, if your power outage caused a hardware
problem that corrupted your log file, you could still restore from your most
recent database backup and then apply your log backups. At most, you would
lose one half hour of work. If only data files were lost, you could backup
the current log with NO_TRUNCATE and then restore your database and log
backups. No data would be lost in this case.
In the SIMPLE recovery model, your only recourse after losing data or log
files is to restore from your most recent database backup. All data
modifications since the backup would be lost.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
>>--Original Message--
>>Regardless of the recovery model, each database is
> automatically recovered
>>when the instance starts. Data are read from the
> transaction log since the
>>last checkpoint and applied to the database. Uncommitted
> transactions are
>>then rolled back. The end result is that the database is
> recovered to the
>>point of the failure, less uncommitted transactions.
>>Your FULL recovery model and log backups provide extra
> protection in the
>>event of media loss due to hardware failure or data
> corruption.
>>--
>>Hope this helps.
>>Dan Guzman
>>SQL Server MVP
>>"Peter" <anonymous@.discussions.microsoft.com> wrote in
> message
>>news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
>> We encounter a power failure for about half an hour and
>> the SQL Server 2000 is back again.
>> For production databases, we use FULL Recovery Model
> with
>> Transaction Log backed up every half an hour. After
> power
>> is up, everything works properly.
>> I would like to know what happens to the SQL Server 2000
>> when the power fails and how the data is recovered when
>> power is up again.
>> Thanks
>>
>>.

Power Failure for SQL Server 2000

We encounter a power failure for about half an hour and
the SQL Server 2000 is back again.
For production databases, we use FULL Recovery Model with
Transaction Log backed up every half an hour. After power
is up, everything works properly.
I would like to know what happens to the SQL Server 2000
when the power fails and how the data is recovered when
power is up again.
Thanks
Regardless of the recovery model, each database is automatically recovered
when the instance starts. Data are read from the transaction log since the
last checkpoint and applied to the database. Uncommitted transactions are
then rolled back. The end result is that the database is recovered to the
point of the failure, less uncommitted transactions.
Your FULL recovery model and log backups provide extra protection in the
event of media loss due to hardware failure or data corruption.
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
> We encounter a power failure for about half an hour and
> the SQL Server 2000 is back again.
> For production databases, we use FULL Recovery Model with
> Transaction Log backed up every half an hour. After power
> is up, everything works properly.
> I would like to know what happens to the SQL Server 2000
> when the power fails and how the data is recovered when
> power is up again.
> Thanks
|||Dear Dan,
Thank you for your advice.
However, for SIMPLE Recovery Model, there will be no
transaction log backup. To what state does the database
recovered to ?
Besides, would you mind to elaborate on the extra benefit
of using FULL Recovery Model ?
Thanks again.

>--Original Message--
>Regardless of the recovery model, each database is
automatically recovered
>when the instance starts. Data are read from the
transaction log since the
>last checkpoint and applied to the database. Uncommitted
transactions are
>then rolled back. The end result is that the database is
recovered to the
>point of the failure, less uncommitted transactions.
>Your FULL recovery model and log backups provide extra
protection in the
>event of media loss due to hardware failure or data
corruption.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Peter" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
with[vbcol=seagreen]
power
>
>.
>
|||Peter
<http://vyaskn.tripod.com/sql_server_...ices.htm#Step1
> --administaiting best practices
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...[vbcol=seagreen]
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
> automatically recovered
> transaction log since the
> transactions are
> recovered to the
> protection in the
> corruption.
> message
> with
> power
|||Automatic recovery (what happens when you start SQL Server) doesn't have anything to do with
backups. SQL Server records all modifications in the transaction log, regardless of recovery model.
In simple, SQL Server removes log records from the transaction log when they aren't needed anymore
for this automatic recovery.
Full recovery model allow you to backup transaction log. This has a lot of advantages, like backup
log even of the database becomes corrupt, point in time restore etc.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...[vbcol=seagreen]
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
> automatically recovered
> transaction log since the
> transactions are
> recovered to the
> protection in the
> corruption.
> message
> with
> power
|||To add to the other responses, automatic recovery will recover databases to
the same consistent state regardless of the recovery model.
Separately, database and transaction log backups reduce your vulnerability
to potential data loss. For example, if your power outage caused a hardware
problem that corrupted your log file, you could still restore from your most
recent database backup and then apply your log backups. At most, you would
lose one half hour of work. If only data files were lost, you could backup
the current log with NO_TRUNCATE and then restore your database and log
backups. No data would be lost in this case.
In the SIMPLE recovery model, your only recourse after losing data or log
files is to restore from your most recent database backup. All data
modifications since the backup would be lost.
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...[vbcol=seagreen]
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
> automatically recovered
> transaction log since the
> transactions are
> recovered to the
> protection in the
> corruption.
> message
> with
> power

Power Failure for SQL Server 2000

We encounter a power failure for about half an hour and
the SQL Server 2000 is back again.
For production databases, we use FULL Recovery Model with
Transaction Log backed up every half an hour. After power
is up, everything works properly.
I would like to know what happens to the SQL Server 2000
when the power fails and how the data is recovered when
power is up again.
ThanksRegardless of the recovery model, each database is automatically recovered
when the instance starts. Data are read from the transaction log since the
last checkpoint and applied to the database. Uncommitted transactions are
then rolled back. The end result is that the database is recovered to the
point of the failure, less uncommitted transactions.
Your FULL recovery model and log backups provide extra protection in the
event of media loss due to hardware failure or data corruption.
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
> We encounter a power failure for about half an hour and
> the SQL Server 2000 is back again.
> For production databases, we use FULL Recovery Model with
> Transaction Log backed up every half an hour. After power
> is up, everything works properly.
> I would like to know what happens to the SQL Server 2000
> when the power fails and how the data is recovered when
> power is up again.
> Thanks|||Dear Dan,
Thank you for your advice.
However, for SIMPLE Recovery Model, there will be no
transaction log backup. To what state does the database
recovered to ?
Besides, would you mind to elaborate on the extra benefit
of using FULL Recovery Model ?
Thanks again.

>--Original Message--
>Regardless of the recovery model, each database is
automatically recovered
>when the instance starts. Data are read from the
transaction log since the
>last checkpoint and applied to the database. Uncommitted
transactions are
>then rolled back. The end result is that the database is
recovered to the
>point of the failure, less uncommitted transactions.
>Your FULL recovery model and log backups provide extra
protection in the
>event of media loss due to hardware failure or data
corruption.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Peter" <anonymous@.discussions.microsoft.com> wrote in
message
>news:01f401c5446e$a4183b70$a601280a@.phx.gbl...
with[vbcol=seagreen]
power[vbcol=seagreen]
>
>.
>|||Peter
<.htm#Step1" target="_blank">http://vyaskn.tripod.com/ sql_serve...r />
.htm#Step1
> --administaiting best practices
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...[vbcol=seagreen]
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
>
> automatically recovered
> transaction log since the
> transactions are
> recovered to the
> protection in the
> corruption.
> message
> with
> power|||Automatic recovery (what happens when you start SQL Server) doesn't have any
thing to do with
backups. SQL Server records all modifications in the transaction log, regard
less of recovery model.
In simple, SQL Server removes log records from the transaction log when they
aren't needed anymore
for this automatic recovery.
Full recovery model allow you to backup transaction log. This has a lot of a
dvantages, like backup
log even of the database becomes corrupt, point in time restore etc.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...[vbcol=seagreen]
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
>
> automatically recovered
> transaction log since the
> transactions are
> recovered to the
> protection in the
> corruption.
> message
> with
> power|||To add to the other responses, automatic recovery will recover databases to
the same consistent state regardless of the recovery model.
Separately, database and transaction log backups reduce your vulnerability
to potential data loss. For example, if your power outage caused a hardware
problem that corrupted your log file, you could still restore from your most
recent database backup and then apply your log backups. At most, you would
lose one half hour of work. If only data files were lost, you could backup
the current log with NO_TRUNCATE and then restore your database and log
backups. No data would be lost in this case.
In the SIMPLE recovery model, your only recourse after losing data or log
files is to restore from your most recent database backup. All data
modifications since the backup would be lost.
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter" <anonymous@.discussions.microsoft.com> wrote in message
news:077101c54475$9661ee70$a501280a@.phx.gbl...[vbcol=seagreen]
> Dear Dan,
> Thank you for your advice.
> However, for SIMPLE Recovery Model, there will be no
> transaction log backup. To what state does the database
> recovered to ?
> Besides, would you mind to elaborate on the extra benefit
> of using FULL Recovery Model ?
> Thanks again.
>
> automatically recovered
> transaction log since the
> transactions are
> recovered to the
> protection in the
> corruption.
> message
> with
> power

Posts to the Newsgroups

Question:
I have posted several times to this newsgroup - going back at least six
months. I needed to refer back to one of those posts. But when I do a search
on my name, the results only show four posts?!?
I know thi isn't right because I've done the exact same search and received
a LOT more results than I'm getting this time around. The results are only
showing posts from July forward.
What's the deal?
Thanks!
The NNTP servers are purged of posts older than 90 days. groups.google.com
if your friend.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:C555008F-91E5-435F-8BF5-FD513D95D948@.microsoft.com...
> Question:
> I have posted several times to this newsgroup - going back at least six
> months. I needed to refer back to one of those posts. But when I do a
search
> on my name, the results only show four posts?!?
> I know thi isn't right because I've done the exact same search and
received
> a LOT more results than I'm getting this time around. The results are only
> showing posts from July forward.
> What's the deal?
> Thanks!

POST BACK TO SERVER

hi all,

i want to filter data from a database using parameters supplied by the user via textboxes. i've been able to write the select statement. my problem now is, the code behind for the "view data" button. do i do "sqldatasource1.select" orpost the databack to theserver? if i'm topostback to theserver, whats the code i should use?

protected void button1_Click(object sender, Eventargs e)

{

????

}

---

I guess it depends. Are you simply displaying data within something like a GridView? If so, then just use GridView.DataBind() and set your Parameters within the SqlDataSource.Selecting event. You could also set up your Parameters to be ControlParameters and point them directly to your TextBoxes.

|||

well i had done that already. it was just the code behind i needed. i didnt put any code and at runtime i clicked the button and it posted to the server. so i guess thats all i need. thanks for the input though

Possible use or import a MySQL database in SQL Server 2005?

Hi all,
I am developing a web application and the back end is MySQL database.

Now I want to shift all the data to SQL Server 2005.

Is there any method to do it?

Thanks

Tomy

Hi,

You can try to use SQL Server Integration Services to do the import/export. Please check the following link for more information

http://msdn2.microsoft.com/en-us/library/ms141026.aspx

HTH. If this does not answer your question, please feel free to mark the post as Not Answered and reply. Thank you!

Possible back door?

Hi I'm new to SQL and I've been asked to help my company with this server
(Windows 2003). Some history of what is going on is that the company is not
happy with their current tech situation and are in the process of getting
rid of their current tech and he knows it. This is where I come in like I
said have been asked to help with this situation. But I'm located at
different location so one of the first things the company wanted me to do is
setup an link between My loction and the other location using the internet.
So my first steps before opening up the the company was to try and secure th
e
system. But what I found is that the current tech is login in to the system
with an account called "sqlagentcmdexec" and on this account there is no
password (In my mind a big problem becauce I think this account was setup
with admin privileges). So when I was checking out the current user list and
their privileges this account in question was not there with all of the othe
r
accounts. I found a coulpe of articles that tells me a little about the
account but not a whole lot. So with all of that in mind what should I try t
o
do? Can I add a password to this account? Can I Find out what the account
privileges are and lower them if the are admin? If it is possible to lower
the account privileges what might be some of the side effects? Could there
be similar hiden accounts on this system and finally what would the best
thing to do in this situation?
Thank you for your time and help!What SQL Server version is used at this company?
I don't think such an account is created in the last two versions of SQL
Server : 2000 and 2005. It might be left from an older SQL Server
installation.
The following KB article has some information on this account:
http://support.microsoft.com/?id=264155
You could also ask for more information on the SQL Server Tools forum:
http://forums.microsoft.com/MSDN/Sh...ID=84&SiteID=1. You can
find answers about SQL Agent topics there.
Thanks
Laurentiu Cristofor [MSFT]
Software Design Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"josh" <josh@.discussions.microsoft.com> wrote in message
news:F389E9E2-9716-4C26-8DC3-BADBFFFE810B@.microsoft.com...
> Hi I'm new to SQL and I've been asked to help my company with this server
> (Windows 2003). Some history of what is going on is that the company is
> not
> happy with their current tech situation and are in the process of getting
> rid of their current tech and he knows it. This is where I come in like I
> said have been asked to help with this situation. But I'm located at
> different location so one of the first things the company wanted me to do
> is
> setup an link between My loction and the other location using the
> internet.
> So my first steps before opening up the the company was to try and secure
> the
> system. But what I found is that the current tech is login in to the
> system
> with an account called "sqlagentcmdexec" and on this account there is no
> password (In my mind a big problem becauce I think this account was setup
> with admin privileges). So when I was checking out the current user list
> and
> their privileges this account in question was not there with all of the
> other
> accounts. I found a coulpe of articles that tells me a little about the
> account but not a whole lot. So with all of that in mind what should I try
> to
> do? Can I add a password to this account? Can I Find out what the account
> privileges are and lower them if the are admin? If it is possible to lower
> the account privileges what might be some of the side effects? Could
> there
> be similar hiden accounts on this system and finally what would the best
> thing to do in this situation?
> Thank you for your time and help!|||To add to Laurentiu's response, the local SqlAgentCmdExec account is created
during a SQL 7 install for use as the SQL Agent Proxy account. The password
should not be blank and is managed entirely by SQL Server. You can reset
the account password from Enterprise Manager per the article link Laurentiu
provided.
Hope this helps.
Dan Guzman
SQL Server MVP
"josh" <josh@.discussions.microsoft.com> wrote in message
news:F389E9E2-9716-4C26-8DC3-BADBFFFE810B@.microsoft.com...
> Hi I'm new to SQL and I've been asked to help my company with this server
> (Windows 2003). Some history of what is going on is that the company is
> not
> happy with their current tech situation and are in the process of getting
> rid of their current tech and he knows it. This is where I come in like I
> said have been asked to help with this situation. But I'm located at
> different location so one of the first things the company wanted me to do
> is
> setup an link between My loction and the other location using the
> internet.
> So my first steps before opening up the the company was to try and secure
> the
> system. But what I found is that the current tech is login in to the
> system
> with an account called "sqlagentcmdexec" and on this account there is no
> password (In my mind a big problem becauce I think this account was setup
> with admin privileges). So when I was checking out the current user list
> and
> their privileges this account in question was not there with all of the
> other
> accounts. I found a coulpe of articles that tells me a little about the
> account but not a whole lot. So with all of that in mind what should I try
> to
> do? Can I add a password to this account? Can I Find out what the account
> privileges are and lower them if the are admin? If it is possible to lower
> the account privileges what might be some of the side effects? Could
> there
> be similar hiden accounts on this system and finally what would the best
> thing to do in this situation?
> Thank you for your time and help!