Recovering SQL login & database

Hello all,
I appologize in advance if I posted in too many, or the wrong newsgroup.
A client of mine contacted me earlier regarding an issue they are having
with their MS SQL server. They use SQL mostly for timeclock entry for
employee's entering and leaving the building during the start of, and end of
the workday. However during the phone call the guy explained to me that
they are now no longer able to log in through the web-interface on the
server using the default login/password for MS SQL. He wondered if the
database itself had become corrupted, but when I began asking a series of
questions, he did seem to suggest that the timeclock information can get
entered into the database with a confirmation that it was entered.
So for the moment it appears that they are locked out of MS SQL. I don't
know how or why as this was just a pre-liminary phone call and I am
expecting to hear from them again shortly. However what is everyone's
thoughts here on password/username recovery for MS SQL? What if the
database did get corrupted, what are recovery options. As far as I know
this client does NOT have a backup server or solution in place.
Brad
"Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> I appologize in advance if I posted in too many, or the wrong newsgroup.
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and end
> of the workday. However during the phone call the guy explained to me
> that they are now no longer able to log in through the web-interface on
> the server using the default login/password for MS SQL. He wondered if
> the database itself had become corrupted, but when I began asking a series
> of questions, he did seem to suggest that the timeclock information can
> get entered into the database with a confirmation that it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
> Brad
>
You've given no reason to assume the database is corrupt. Do you have an
administrator login for SQL Server? Do they know the SA password? If not,
you should still be able to log in as a domain admin or local admin for that
server using integrated security. Then you can check that the login they are
using for the site does in fact exist and you can change the password if
necessary. There is no such thing as a default login and password for SQL
Server.
Before you do anything you should of course make sure they have a valid
backup on disc or tape. If they are running in deathwish mode (no backups)
and you can't even login then shutdown the SQL service (only when the system
isn't in use) and backup the physical files from the data folder as a first
step.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||"Deathwish mode". I am gonna have to "borrow" that phrase. It is too good
to leave lying around unused.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:ef9Pkz3UGHA.4740@.TK2MSFTNGP14.phx.gbl...
> "Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
> news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> "Deathwish mode". I am gonna have to "borrow" that phrase. It is too
> good to leave lying around unused.
>
Hope you don't have cause to use it too often :-)
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||You hang around the newsgroups enough to know how often I will have to use
it.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uCElmA4UGHA.4956@.TK2MSFTNGP09.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> Hope you don't have cause to use it too often :-)
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||As I stated in my orginial post, I was going on based what the client told
me across the phone of intial symptoms, their concerns, and using that to
prepare for a possible client job. That is why I posted here, as part of my
quick pre-preperation to better understand what I may or may not see when I
arrive on the site. Normally what a client says on the phone is always the
opposite of what I find, so any information I posted was strictly from the
quick and informal phone call.
The good news is that in the end it was discovered that a heavily medicated
and disgruntled employee decided to start making unauthorized changes to the
server which appearantly included logon information. As far as I know they
are running in "Deathwish mode" because there are no onsite backups, no
backup proceedures, etc.

> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.
sql

Recovering SQL login & database

Hello all,
I appologize in advance if I posted in too many, or the wrong newsgroup.
A client of mine contacted me earlier regarding an issue they are having
with their MS SQL server. They use SQL mostly for timeclock entry for
employee's entering and leaving the building during the start of, and end of
the workday. However during the phone call the guy explained to me that
they are now no longer able to log in through the web-interface on the
server using the default login/password for MS SQL. He wondered if the
database itself had become corrupted, but when I began asking a series of
questions, he did seem to suggest that the timeclock information can get
entered into the database with a confirmation that it was entered.
So for the moment it appears that they are locked out of MS SQL. I don't
know how or why as this was just a pre-liminary phone call and I am
expecting to hear from them again shortly. However what is everyone's
thoughts here on password/username recovery for MS SQL? What if the
database did get corrupted, what are recovery options. As far as I know
this client does NOT have a backup server or solution in place.
Brad
"Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> I appologize in advance if I posted in too many, or the wrong newsgroup.
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and end
> of the workday. However during the phone call the guy explained to me
> that they are now no longer able to log in through the web-interface on
> the server using the default login/password for MS SQL. He wondered if
> the database itself had become corrupted, but when I began asking a series
> of questions, he did seem to suggest that the timeclock information can
> get entered into the database with a confirmation that it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
> Brad
>
You've given no reason to assume the database is corrupt. Do you have an
administrator login for SQL Server? Do they know the SA password? If not,
you should still be able to log in as a domain admin or local admin for that
server using integrated security. Then you can check that the login they are
using for the site does in fact exist and you can change the password if
necessary. There is no such thing as a default login and password for SQL
Server.
Before you do anything you should of course make sure they have a valid
backup on disc or tape. If they are running in deathwish mode (no backups)
and you can't even login then shutdown the SQL service (only when the system
isn't in use) and backup the physical files from the data folder as a first
step.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||"Deathwish mode". I am gonna have to "borrow" that phrase. It is too good
to leave lying around unused.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:ef9Pkz3UGHA.4740@.TK2MSFTNGP14.phx.gbl...
> "Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
> news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> "Deathwish mode". I am gonna have to "borrow" that phrase. It is too
> good to leave lying around unused.
>
Hope you don't have cause to use it too often :-)
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||You hang around the newsgroups enough to know how often I will have to use
it.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uCElmA4UGHA.4956@.TK2MSFTNGP09.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> Hope you don't have cause to use it too often :-)
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||As I stated in my orginial post, I was going on based what the client told
me across the phone of intial symptoms, their concerns, and using that to
prepare for a possible client job. That is why I posted here, as part of my
quick pre-preperation to better understand what I may or may not see when I
arrive on the site. Normally what a client says on the phone is always the
opposite of what I find, so any information I posted was strictly from the
quick and informal phone call.
The good news is that in the end it was discovered that a heavily medicated
and disgruntled employee decided to start making unauthorized changes to the
server which appearantly included logon information. As far as I know they
are running in "Deathwish mode" because there are no onsite backups, no
backup proceedures, etc.

> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.

Recovering SQL login & database

Hello all,
I appologize in advance if I posted in too many, or the wrong newsgroup.
A client of mine contacted me earlier regarding an issue they are having
with their MS SQL server. They use SQL mostly for timeclock entry for
employee's entering and leaving the building during the start of, and end of
the workday. However during the phone call the guy explained to me that
they are now no longer able to log in through the web-interface on the
server using the default login/password for MS SQL. He wondered if the
database itself had become corrupted, but when I began asking a series of
questions, he did seem to suggest that the timeclock information can get
entered into the database with a confirmation that it was entered.
So for the moment it appears that they are locked out of MS SQL. I don't
know how or why as this was just a pre-liminary phone call and I am
expecting to hear from them again shortly. However what is everyone's
thoughts here on password/username recovery for MS SQL? What if the
database did get corrupted, what are recovery options. As far as I know
this client does NOT have a backup server or solution in place.
Brad
"Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> I appologize in advance if I posted in too many, or the wrong newsgroup.
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and end
> of the workday. However during the phone call the guy explained to me
> that they are now no longer able to log in through the web-interface on
> the server using the default login/password for MS SQL. He wondered if
> the database itself had become corrupted, but when I began asking a series
> of questions, he did seem to suggest that the timeclock information can
> get entered into the database with a confirmation that it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
> Brad
>
You've given no reason to assume the database is corrupt. Do you have an
administrator login for SQL Server? Do they know the SA password? If not,
you should still be able to log in as a domain admin or local admin for that
server using integrated security. Then you can check that the login they are
using for the site does in fact exist and you can change the password if
necessary. There is no such thing as a default login and password for SQL
Server.
Before you do anything you should of course make sure they have a valid
backup on disc or tape. If they are running in deathwish mode (no backups)
and you can't even login then shutdown the SQL service (only when the system
isn't in use) and backup the physical files from the data folder as a first
step.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||"Deathwish mode". I am gonna have to "borrow" that phrase. It is too good
to leave lying around unused.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:ef9Pkz3UGHA.4740@.TK2MSFTNGP14.phx.gbl...
> "Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
> news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> "Deathwish mode". I am gonna have to "borrow" that phrase. It is too
> good to leave lying around unused.
>
Hope you don't have cause to use it too often :-)
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||You hang around the newsgroups enough to know how often I will have to use
it.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uCElmA4UGHA.4956@.TK2MSFTNGP09.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> Hope you don't have cause to use it too often :-)
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||As I stated in my orginial post, I was going on based what the client told
me across the phone of intial symptoms, their concerns, and using that to
prepare for a possible client job. That is why I posted here, as part of my
quick pre-preperation to better understand what I may or may not see when I
arrive on the site. Normally what a client says on the phone is always the
opposite of what I find, so any information I posted was strictly from the
quick and informal phone call.
The good news is that in the end it was discovered that a heavily medicated
and disgruntled employee decided to start making unauthorized changes to the
server which appearantly included logon information. As far as I know they
are running in "Deathwish mode" because there are no onsite backups, no
backup proceedures, etc.

> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.

Recovering SQL login & database

Hello all,
I appologize in advance if I posted in too many, or the wrong newsgroup.
A client of mine contacted me earlier regarding an issue they are having
with their MS SQL server. They use SQL mostly for timeclock entry for
employee's entering and leaving the building during the start of, and end of
the workday. However during the phone call the guy explained to me that
they are now no longer able to log in through the web-interface on the
server using the default login/password for MS SQL. He wondered if the
database itself had become corrupted, but when I began asking a series of
questions, he did seem to suggest that the timeclock information can get
entered into the database with a confirmation that it was entered.
So for the moment it appears that they are locked out of MS SQL. I don't
know how or why as this was just a pre-liminary phone call and I am
expecting to hear from them again shortly. However what is everyone's
thoughts here on password/username recovery for MS SQL? What if the
database did get corrupted, what are recovery options. As far as I know
this client does NOT have a backup server or solution in place.
BradBradley Walker (bawalkerREMOVE@.THISmodemnet.net) writes:
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and
> end of the workday. However during the phone call the guy explained to
> me that they are now no longer able to log in through the web-interface
> on the server using the default login/password for MS SQL. He wondered
> if the database itself had become corrupted, but when I began asking a
> series of questions, he did seem to suggest that the timeclock
> information can get entered into the database with a confirmation that
> it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
First of all, which version of SQL Server are they running, and on
which operating system?
It is not clear here where this login/password lives. It this a
username/password for SQL authentication? Or does the web page login
with Windows Authnetication, and then has its own username/password
validated within or outside SQL Server.
In case they are using SQL authentication to login, username/password
information is in the master database, which is not there the timeclock
entries are. I hope!
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||"Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> I appologize in advance if I posted in too many, or the wrong newsgroup.
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and end
> of the workday. However during the phone call the guy explained to me
> that they are now no longer able to log in through the web-interface on
> the server using the default login/password for MS SQL. He wondered if
> the database itself had become corrupted, but when I began asking a series
> of questions, he did seem to suggest that the timeclock information can
> get entered into the database with a confirmation that it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
> Brad
>
You've given no reason to assume the database is corrupt. Do you have an
administrator login for SQL Server? Do they know the SA password? If not,
you should still be able to log in as a domain admin or local admin for that
server using integrated security. Then you can check that the login they are
using for the site does in fact exist and you can change the password if
necessary. There is no such thing as a default login and password for SQL
Server.
Before you do anything you should of course make sure they have a valid
backup on disc or tape. If they are running in deathwish mode (no backups)
and you can't even login then shutdown the SQL service (only when the system
isn't in use) and backup the physical files from the data folder as a first
step.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||"Deathwish mode". I am gonna have to "borrow" that phrase. It is too good
to leave lying around unused.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:ef9Pkz3UGHA.4740@.TK2MSFTNGP14.phx.gbl...
> "Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
> news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
>> Hello all,
>> I appologize in advance if I posted in too many, or the wrong newsgroup.
>> A client of mine contacted me earlier regarding an issue they are having
>> with their MS SQL server. They use SQL mostly for timeclock entry for
>> employee's entering and leaving the building during the start of, and end
>> of the workday. However during the phone call the guy explained to me
>> that they are now no longer able to log in through the web-interface on
>> the server using the default login/password for MS SQL. He wondered if
>> the database itself had become corrupted, but when I began asking a
>> series of questions, he did seem to suggest that the timeclock
>> information can get entered into the database with a confirmation that it
>> was entered.
>> So for the moment it appears that they are locked out of MS SQL. I don't
>> know how or why as this was just a pre-liminary phone call and I am
>> expecting to hear from them again shortly. However what is everyone's
>> thoughts here on password/username recovery for MS SQL? What if the
>> database did get corrupted, what are recovery options. As far as I know
>> this client does NOT have a backup server or solution in place.
>> Brad
>>
> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> "Deathwish mode". I am gonna have to "borrow" that phrase. It is too
> good to leave lying around unused.
>
Hope you don't have cause to use it too often :-)
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||You hang around the newsgroups enough to know how often I will have to use
it. :)
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uCElmA4UGHA.4956@.TK2MSFTNGP09.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
>> "Deathwish mode". I am gonna have to "borrow" that phrase. It is too
>> good to leave lying around unused.
> Hope you don't have cause to use it too often :-)
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||You said they can't login via the web interface on the server using the
default MSSQL login. I don't understand what that means.
Do they have physical access to walk up to the machine?
Can they log into Windows with an administrator windows account?
If yes to the above 2 questions, can they open Enterprise Manager on that
machine, under their windows login with windows authentication?
"Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> I appologize in advance if I posted in too many, or the wrong newsgroup.
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and end
of
> the workday. However during the phone call the guy explained to me that
> they are now no longer able to log in through the web-interface on the
> server using the default login/password for MS SQL. He wondered if the
> database itself had become corrupted, but when I began asking a series of
> questions, he did seem to suggest that the timeclock information can get
> entered into the database with a confirmation that it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
> Brad
>|||As I stated in my orginial post, I was going on based what the client told
me across the phone of intial symptoms, their concerns, and using that to
prepare for a possible client job. That is why I posted here, as part of my
quick pre-preperation to better understand what I may or may not see when I
arrive on the site. Normally what a client says on the phone is always the
opposite of what I find, so any information I posted was strictly from the
quick and informal phone call.
The good news is that in the end it was discovered that a heavily medicated
and disgruntled employee decided to start making unauthorized changes to the
server which appearantly included logon information. As far as I know they
are running in "Deathwish mode" because there are no onsite backups, no
backup proceedures, etc.
> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.

Recovering SQL login & database

Hello all,
I appologize in advance if I posted in too many, or the wrong newsgroup.
A client of mine contacted me earlier regarding an issue they are having
with their MS SQL server. They use SQL mostly for timeclock entry for
employee's entering and leaving the building during the start of, and end of
the workday. However during the phone call the guy explained to me that
they are now no longer able to log in through the web-interface on the
server using the default login/password for MS SQL. He wondered if the
database itself had become corrupted, but when I began asking a series of
questions, he did seem to suggest that the timeclock information can get
entered into the database with a confirmation that it was entered.
So for the moment it appears that they are locked out of MS SQL. I don't
know how or why as this was just a pre-liminary phone call and I am
expecting to hear from them again shortly. However what is everyone's
thoughts here on password/username recovery for MS SQL? What if the
database did get corrupted, what are recovery options. As far as I know
this client does NOT have a backup server or solution in place.
Brad
"Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> I appologize in advance if I posted in too many, or the wrong newsgroup.
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and end
> of the workday. However during the phone call the guy explained to me
> that they are now no longer able to log in through the web-interface on
> the server using the default login/password for MS SQL. He wondered if
> the database itself had become corrupted, but when I began asking a series
> of questions, he did seem to suggest that the timeclock information can
> get entered into the database with a confirmation that it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
> Brad
>
You've given no reason to assume the database is corrupt. Do you have an
administrator login for SQL Server? Do they know the SA password? If not,
you should still be able to log in as a domain admin or local admin for that
server using integrated security. Then you can check that the login they are
using for the site does in fact exist and you can change the password if
necessary. There is no such thing as a default login and password for SQL
Server.
Before you do anything you should of course make sure they have a valid
backup on disc or tape. If they are running in deathwish mode (no backups)
and you can't even login then shutdown the SQL service (only when the system
isn't in use) and backup the physical files from the data folder as a first
step.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||"Deathwish mode". I am gonna have to "borrow" that phrase. It is too good
to leave lying around unused.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:ef9Pkz3UGHA.4740@.TK2MSFTNGP14.phx.gbl...
> "Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
> news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> "Deathwish mode". I am gonna have to "borrow" that phrase. It is too
> good to leave lying around unused.
>
Hope you don't have cause to use it too often :-)
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
|||You hang around the newsgroups enough to know how often I will have to use
it.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uCElmA4UGHA.4956@.TK2MSFTNGP09.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> Hope you don't have cause to use it too often :-)
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>
|||As I stated in my orginial post, I was going on based what the client told
me across the phone of intial symptoms, their concerns, and using that to
prepare for a possible client job. That is why I posted here, as part of my
quick pre-preperation to better understand what I may or may not see when I
arrive on the site. Normally what a client says on the phone is always the
opposite of what I find, so any information I posted was strictly from the
quick and informal phone call.
The good news is that in the end it was discovered that a heavily medicated
and disgruntled employee decided to start making unauthorized changes to the
server which appearantly included logon information. As far as I know they
are running in "Deathwish mode" because there are no onsite backups, no
backup proceedures, etc.

> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.

Recovering SQL login & database

Hello all,
I appologize in advance if I posted in too many, or the wrong newsgroup.
A client of mine contacted me earlier regarding an issue they are having
with their MS SQL server. They use SQL mostly for timeclock entry for
employee's entering and leaving the building during the start of, and end of
the workday. However during the phone call the guy explained to me that
they are now no longer able to log in through the web-interface on the
server using the default login/password for MS SQL. He wondered if the
database itself had become corrupted, but when I began asking a series of
questions, he did seem to suggest that the timeclock information can get
entered into the database with a confirmation that it was entered.
So for the moment it appears that they are locked out of MS SQL. I don't
know how or why as this was just a pre-liminary phone call and I am
expecting to hear from them again shortly. However what is everyone's
thoughts here on password/username recovery for MS SQL? What if the
database did get corrupted, what are recovery options. As far as I know
this client does NOT have a backup server or solution in place.
Brad"Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> Hello all,
> I appologize in advance if I posted in too many, or the wrong newsgroup.
> A client of mine contacted me earlier regarding an issue they are having
> with their MS SQL server. They use SQL mostly for timeclock entry for
> employee's entering and leaving the building during the start of, and end
> of the workday. However during the phone call the guy explained to me
> that they are now no longer able to log in through the web-interface on
> the server using the default login/password for MS SQL. He wondered if
> the database itself had become corrupted, but when I began asking a series
> of questions, he did seem to suggest that the timeclock information can
> get entered into the database with a confirmation that it was entered.
> So for the moment it appears that they are locked out of MS SQL. I don't
> know how or why as this was just a pre-liminary phone call and I am
> expecting to hear from them again shortly. However what is everyone's
> thoughts here on password/username recovery for MS SQL? What if the
> database did get corrupted, what are recovery options. As far as I know
> this client does NOT have a backup server or solution in place.
> Brad
>
You've given no reason to assume the database is corrupt. Do you have an
administrator login for SQL Server? Do they know the SA password? If not,
you should still be able to log in as a domain admin or local admin for that
server using integrated security. Then you can check that the login they are
using for the site does in fact exist and you can change the password if
necessary. There is no such thing as a default login and password for SQL
Server.
Before you do anything you should of course make sure they have a valid
backup on disc or tape. If they are running in deathwish mode (no backups)
and you can't even login then shutdown the SQL service (only when the system
isn't in use) and backup the physical files from the data folder as a first
step.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||"Deathwish mode". I am gonna have to "borrow" that phrase. It is too good
to leave lying around unused.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:ef9Pkz3UGHA.4740@.TK2MSFTNGP14.phx.gbl...
> "Bradley Walker" <bawalkerREMOVE@.THISmodemnet.net> wrote in message
> news:O%236hPz2UGHA.4276@.TK2MSFTNGP10.phx.gbl...
> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> "Deathwish mode". I am gonna have to "borrow" that phrase. It is too
> good to leave lying around unused.
>
Hope you don't have cause to use it too often :-)
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||You hang around the newsgroups enough to know how often I will have to use
it.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:uCElmA4UGHA.4956@.TK2MSFTNGP09.phx.gbl...
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OmjcU13UGHA.5588@.TK2MSFTNGP09.phx.gbl...
> Hope you don't have cause to use it too often :-)
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||As I stated in my orginial post, I was going on based what the client told
me across the phone of intial symptoms, their concerns, and using that to
prepare for a possible client job. That is why I posted here, as part of my
quick pre-preperation to better understand what I may or may not see when I
arrive on the site. Normally what a client says on the phone is always the
opposite of what I find, so any information I posted was strictly from the
quick and informal phone call.
The good news is that in the end it was discovered that a heavily medicated
and disgruntled employee decided to start making unauthorized changes to the
server which appearantly included logon information. As far as I know they
are running in "Deathwish mode" because there are no onsite backups, no
backup proceedures, etc.

> You've given no reason to assume the database is corrupt. Do you have an
> administrator login for SQL Server? Do they know the SA password? If not,
> you should still be able to log in as a domain admin or local admin for
> that server using integrated security. Then you can check that the login
> they are using for the site does in fact exist and you can change the
> password if necessary. There is no such thing as a default login and
> password for SQL Server.
> Before you do anything you should of course make sure they have a valid
> backup on disc or tape. If they are running in deathwish mode (no backups)
> and you can't even login then shutdown the SQL service (only when the
> system isn't in use) and backup the physical files from the data folder as
> a first step.sql

Recovering dropped SQL database

I am in a big trouble ,

accidently i have issued a DROP DATABASE XXX command in the sql client, thinking its a local server....... The whole 4 months of database database is now dropped.

Please help me , how can i recover the database ....

thanks in advance

If you don′t have a backup of the data, I will have to tell you, that there is no UNDO button for that. Sorry.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.desql

Recovering (local) server and Restoring a Dabase from a clients backup

Hi all,
I'm running sql server 2000.
I've a client who has given me a large database to develope against.
I don't have a (local) server anymore. Can't remember why.
Whats the easiest way to recover (local) - I'm happy to reinstall and start
from a fresh (local).
Also, it looks as though the client has backed up their db.
Am I able to restore to my (local) from their backup?
Thanks,
baz
Yes you can restore it. You don't need to restore it locally unless you
want to. I would just place the backup some place where your development
server can see it, and then use EM to restore from the database backup.
Make sure you type in the name of the database you want to create from the
restore, so you don't overlay some other database.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I'm running sql server 2000.
> I've a client who has given me a large database to develope against.
> I don't have a (local) server anymore. Can't remember why.
> Whats the easiest way to recover (local) - I'm happy to reinstall and
start
> from a fresh (local).
> Also, it looks as though the client has backed up their db.
> Am I able to restore to my (local) from their backup?
> Thanks,
> baz
>
>
|||Yes you can restore it. You don't need to restore it locally unless you
want to. I would just place the backup some place where your development
server can see it, and then use EM to restore from the database backup.
Make sure you type in the name of the database you want to create from the
restore, so you don't overlay some other database.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I'm running sql server 2000.
> I've a client who has given me a large database to develope against.
> I don't have a (local) server anymore. Can't remember why.
> Whats the easiest way to recover (local) - I'm happy to reinstall and
start
> from a fresh (local).
> Also, it looks as though the client has backed up their db.
> Am I able to restore to my (local) from their backup?
> Thanks,
> baz
>
>
|||Hi Greg,
Thanks for the quick reply.
Thats great news.
I'm trying to imulate the client setup as closely as possible.
I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
So, I do want a (local) server.
Anyone have any ideas on how to reinstall or recover the (local) server?
I reinstalled sql server last week but the (local) didn't re-appear.
And it looks like I have to have a database name already there to be able to
recover to it.
Any suggestions?
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Yes you can restore it. You don't need to restore it locally unless you
> want to. I would just place the backup some place where your development
> server can see it, and then use EM to restore from the database backup.
> Make sure you type in the name of the database you want to create from the
> restore, so you don't overlay some other database.
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> start
>
|||Hi Greg,
Thanks for the quick reply.
Thats great news.
I'm trying to imulate the client setup as closely as possible.
I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
So, I do want a (local) server.
Anyone have any ideas on how to reinstall or recover the (local) server?
I reinstalled sql server last week but the (local) didn't re-appear.
And it looks like I have to have a database name already there to be able to
recover to it.
Any suggestions?
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Yes you can restore it. You don't need to restore it locally unless you
> want to. I would just place the backup some place where your development
> server can see it, and then use EM to restore from the database backup.
> Make sure you type in the name of the database you want to create from the
> restore, so you don't overlay some other database.
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> start
>
|||Attempting to sort out the Database name.
Just added a new database with the same name as the clients.
And used the All Task | Restore Database.
3.5 gigs available on the H: drive where I have the backed up database.
H: is where the .mdf resides as well.
3.1 gigs available of the c: drive
The backup itself is 734 megs.
All drives are NTFS
I'm getting this error:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Modify File encountered operating system error 112(There is not enought
space on the disk.) while attempting to expand the physical file.
Could not adjust the space allocation for file 'x-Log'.
Restore Datbase is terminating abnormally.
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> Hi Greg,
> Thanks for the quick reply.
> Thats great news.
> --
> I'm trying to imulate the client setup as closely as possible.
> I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> So, I do want a (local) server.
> Anyone have any ideas on how to reinstall or recover the (local) server?
> I reinstalled sql server last week but the (local) didn't re-appear.
>
> And it looks like I have to have a database name already there to be able
to[vbcol=seagreen]
> recover to it.
> Any suggestions?
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
development[vbcol=seagreen]
the
> ----
> --
> ----
> --
>
|||Attempting to sort out the Database name.
Just added a new database with the same name as the clients.
And used the All Task | Restore Database.
3.5 gigs available on the H: drive where I have the backed up database.
H: is where the .mdf resides as well.
3.1 gigs available of the c: drive
The backup itself is 734 megs.
All drives are NTFS
I'm getting this error:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Modify File encountered operating system error 112(There is not enought
space on the disk.) while attempting to expand the physical file.
Could not adjust the space allocation for file 'x-Log'.
Restore Datbase is terminating abnormally.
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> Hi Greg,
> Thanks for the quick reply.
> Thats great news.
> --
> I'm trying to imulate the client setup as closely as possible.
> I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> So, I do want a (local) server.
> Anyone have any ideas on how to reinstall or recover the (local) server?
> I reinstalled sql server last week but the (local) didn't re-appear.
>
> And it looks like I have to have a database name already there to be able
to[vbcol=seagreen]
> recover to it.
> Any suggestions?
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
development[vbcol=seagreen]
the
> ----
> --
> ----
> --
>
|||Make sure you are restoring the data and log files to a valid drive on your
local server. When your customer made the backup, the paths where the data
files resided on the customer's server are also recorded. When you now
restore the backup, SQL Server will by default try to restore the files to
the same location. You may need to change these paths. Since you are using
Enterprise Manager, look in the Options tab in the Restore database dialog.
If using Query Analyzer, look up the RESTORE FILELISTONLY .. and RESTORE
DATABASE ... WITH MOVE ... syntax.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23mPKjQWXEHA.736@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Attempting to sort out the Database name.
> Just added a new database with the same name as the clients.
> And used the All Task | Restore Database.
> 3.5 gigs available on the H: drive where I have the backed up database.
> H: is where the .mdf resides as well.
> 3.1 gigs available of the c: drive
> The backup itself is 734 megs.
> All drives are NTFS
> I'm getting this error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Modify File encountered operating system error 112(There is not enought
> space on the disk.) while attempting to expand the physical file.
> Could not adjust the space allocation for file 'x-Log'.
> Restore Datbase is terminating abnormally.
> Thanks,
> baz
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
able[vbcol=seagreen]
> to
you[vbcol=seagreen]
> development
backup.[vbcol=seagreen]
> the
> ----
> ----
and
>
|||Make sure you are restoring the data and log files to a valid drive on your
local server. When your customer made the backup, the paths where the data
files resided on the customer's server are also recorded. When you now
restore the backup, SQL Server will by default try to restore the files to
the same location. You may need to change these paths. Since you are using
Enterprise Manager, look in the Options tab in the Restore database dialog.
If using Query Analyzer, look up the RESTORE FILELISTONLY .. and RESTORE
DATABASE ... WITH MOVE ... syntax.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23mPKjQWXEHA.736@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Attempting to sort out the Database name.
> Just added a new database with the same name as the clients.
> And used the All Task | Restore Database.
> 3.5 gigs available on the H: drive where I have the backed up database.
> H: is where the .mdf resides as well.
> 3.1 gigs available of the c: drive
> The backup itself is 734 megs.
> All drives are NTFS
> I'm getting this error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Modify File encountered operating system error 112(There is not enought
> space on the disk.) while attempting to expand the physical file.
> Could not adjust the space allocation for file 'x-Log'.
> Restore Datbase is terminating abnormally.
> Thanks,
> baz
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
able[vbcol=seagreen]
> to
you[vbcol=seagreen]
> development
backup.[vbcol=seagreen]
> the
> ----
> ----
and
>
|||Hi Peter,
Thanks for the reply.
You have to have a database already setup on your server to restore to.
So my database was only 1 k .
Ten after the failed attempt it is was 750megs.
Had another look thru google.
Looks like some others were having the same prob.
Theirs turned out to be a severely defragmented hard drive.
I've had a look thru mine with DiskKeeper.
Mine is also severely defragmented as well.
I've been defraggin all day but I can't get DiskKeeper to continue defraggin
on its own
I have to keep starting it and it only defrage 50 frags at a time? Who
knows ...
I'll update a followup when I have some news...

Recovering (local) server and Restoring a Dabase from a clients backup

Hi all,
I'm running sql server 2000.
I've a client who has given me a large database to develope against.
I don't have a (local) server anymore. Can't remember why.
Whats the easiest way to recover (local) - I'm happy to reinstall and start
from a fresh (local).
Also, it looks as though the client has backed up their db.
Am I able to restore to my (local) from their backup?
Thanks,
bazYes you can restore it. You don't need to restore it locally unless you
want to. I would just place the backup some place where your development
server can see it, and then use EM to restore from the database backup.
Make sure you type in the name of the database you want to create from the
restore, so you don't overlay some other database.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I'm running sql server 2000.
> I've a client who has given me a large database to develope against.
> I don't have a (local) server anymore. Can't remember why.
> Whats the easiest way to recover (local) - I'm happy to reinstall and
start
> from a fresh (local).
> Also, it looks as though the client has backed up their db.
> Am I able to restore to my (local) from their backup?
> Thanks,
> baz
>
>|||Hi Greg,
Thanks for the quick reply.
Thats great news.
--
I'm trying to imulate the client setup as closely as possible.
I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
So, I do want a (local) server.
Anyone have any ideas on how to reinstall or recover the (local) server?
I reinstalled sql server last week but the (local) didn't re-appear.
And it looks like I have to have a database name already there to be able to
recover to it.
Any suggestions?
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Yes you can restore it. You don't need to restore it locally unless you
> want to. I would just place the backup some place where your development
> server can see it, and then use EM to restore from the database backup.
> Make sure you type in the name of the database you want to create from the
> restore, so you don't overlay some other database.
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> > Hi all,
> >
> > I'm running sql server 2000.
> >
> > I've a client who has given me a large database to develope against.
> >
> > I don't have a (local) server anymore. Can't remember why.
> >
> > Whats the easiest way to recover (local) - I'm happy to reinstall and
> start
> > from a fresh (local).
> >
> > Also, it looks as though the client has backed up their db.
> > Am I able to restore to my (local) from their backup?
> >
> > Thanks,
> > baz
> >
> >
> >
> >
>|||Attempting to sort out the Database name.
Just added a new database with the same name as the clients.
And used the All Task | Restore Database.
3.5 gigs available on the H: drive where I have the backed up database.
H: is where the .mdf resides as well.
3.1 gigs available of the c: drive
The backup itself is 734 megs.
All drives are NTFS
I'm getting this error:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Modify File encountered operating system error 112(There is not enought
space on the disk.) while attempting to expand the physical file.
Could not adjust the space allocation for file 'x-Log'.
Restore Datbase is terminating abnormally.
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> Hi Greg,
> Thanks for the quick reply.
> Thats great news.
> --
> I'm trying to imulate the client setup as closely as possible.
> I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> So, I do want a (local) server.
> Anyone have any ideas on how to reinstall or recover the (local) server?
> I reinstalled sql server last week but the (local) didn't re-appear.
>
> And it looks like I have to have a database name already there to be able
to
> recover to it.
> Any suggestions?
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > Yes you can restore it. You don't need to restore it locally unless you
> > want to. I would just place the backup some place where your
development
> > server can see it, and then use EM to restore from the database backup.
> > Make sure you type in the name of the database you want to create from
the
> > restore, so you don't overlay some other database.
> > --
> >
> ----
> --
> ----
> --
> > --
> >
> > Need SQL Server Examples check out my website at
> > http://www.geocities.com/sqlserverexamples
> > "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> > news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> > > Hi all,
> > >
> > > I'm running sql server 2000.
> > >
> > > I've a client who has given me a large database to develope against.
> > >
> > > I don't have a (local) server anymore. Can't remember why.
> > >
> > > Whats the easiest way to recover (local) - I'm happy to reinstall and
> > start
> > > from a fresh (local).
> > >
> > > Also, it looks as though the client has backed up their db.
> > > Am I able to restore to my (local) from their backup?
> > >
> > > Thanks,
> > > baz
> > >
> > >
> > >
> > >
> >
> >
>|||Make sure you are restoring the data and log files to a valid drive on your
local server. When your customer made the backup, the paths where the data
files resided on the customer's server are also recorded. When you now
restore the backup, SQL Server will by default try to restore the files to
the same location. You may need to change these paths. Since you are using
Enterprise Manager, look in the Options tab in the Restore database dialog.
If using Query Analyzer, look up the RESTORE FILELISTONLY .. and RESTORE
DATABASE ... WITH MOVE ... syntax.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23mPKjQWXEHA.736@.TK2MSFTNGP10.phx.gbl...
> Attempting to sort out the Database name.
> Just added a new database with the same name as the clients.
> And used the All Task | Restore Database.
> 3.5 gigs available on the H: drive where I have the backed up database.
> H: is where the .mdf resides as well.
> 3.1 gigs available of the c: drive
> The backup itself is 734 megs.
> All drives are NTFS
> I'm getting this error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Modify File encountered operating system error 112(There is not enought
> space on the disk.) while attempting to expand the physical file.
> Could not adjust the space allocation for file 'x-Log'.
> Restore Datbase is terminating abnormally.
> Thanks,
> baz
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> > Hi Greg,
> >
> > Thanks for the quick reply.
> >
> > Thats great news.
> >
> > --
> > I'm trying to imulate the client setup as closely as possible.
> > I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> > And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> >
> > So, I do want a (local) server.
> >
> > Anyone have any ideas on how to reinstall or recover the (local) server?
> > I reinstalled sql server last week but the (local) didn't re-appear.
> >
> >
> > And it looks like I have to have a database name already there to be
able
> to
> > recover to it.
> >
> > Any suggestions?
> >
> >
> > "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> > news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> > > Yes you can restore it. You don't need to restore it locally unless
you
> > > want to. I would just place the backup some place where your
> development
> > > server can see it, and then use EM to restore from the database
backup.
> > > Make sure you type in the name of the database you want to create from
> the
> > > restore, so you don't overlay some other database.
> > > --
> > >
> >
> ----
> > --
> >
> ----
> > --
> > > --
> > >
> > > Need SQL Server Examples check out my website at
> > > http://www.geocities.com/sqlserverexamples
> > > "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> > > news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> > > > Hi all,
> > > >
> > > > I'm running sql server 2000.
> > > >
> > > > I've a client who has given me a large database to develope against.
> > > >
> > > > I don't have a (local) server anymore. Can't remember why.
> > > >
> > > > Whats the easiest way to recover (local) - I'm happy to reinstall
and
> > > start
> > > > from a fresh (local).
> > > >
> > > > Also, it looks as though the client has backed up their db.
> > > > Am I able to restore to my (local) from their backup?
> > > >
> > > > Thanks,
> > > > baz
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||Hi Peter,
Thanks for the reply.
You have to have a database already setup on your server to restore to.
So my database was only 1 k .
Ten after the failed attempt it is was 750megs.
--
Had another look thru google.
Looks like some others were having the same prob.
Theirs turned out to be a severely defragmented hard drive.
I've had a look thru mine with DiskKeeper.
Mine is also severely defragmented as well.
I've been defraggin all day but I can't get DiskKeeper to continue defraggin
on its own
I have to keep starting it and it only defrage 50 frags at a time? Who
knows ...
I'll update a followup when I have some news...|||Ok I've done it.
DiskKeeper wouldn't defrag enought to make a difference so I had to move my
focus to C: drive.
Still no luck.
I found an older version of w2k on c: drive and removed it.
Defraged with heaps better oucome with diskkeeper.
C: drive then had 4.5 gig free space
Moved backup to C: drive (750 meg)
and created new table on C: drive 1 k - (3.7 gig free on c: drive)
Restored successfully.
now have 3 gig free space
Could have been just the free space restrictions.
Difference between 3.1 failure and 4.5 success.
Anyone know the formula?
Perhaps 3gig / .75 gig failure = 4 times
and 4.5 gig / .75 gig success = 6 times
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:#V7#YyXXEHA.712@.TK2MSFTNGP11.phx.gbl...
> Hi Peter,
> Thanks for the reply.
> You have to have a database already setup on your server to restore
to.
> So my database was only 1 k .
> Ten after the failed attempt it is was 750megs.
> --
>
> Had another look thru google.
> Looks like some others were having the same prob.
> Theirs turned out to be a severely defragmented hard drive.
> I've had a look thru mine with DiskKeeper.
> Mine is also severely defragmented as well.
> I've been defraggin all day but I can't get DiskKeeper to continue
defraggin
> on its own
> I have to keep starting it and it only defrage 50 frags at a time? Who
> knows ...
> I'll update a followup when I have some news...
>|||Don't know if there is such a formula, but it's sure something to keep in
mind. Thx for the update.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23ODumxuXEHA.3944@.tk2msftngp13.phx.gbl...
> Ok I've done it.
> DiskKeeper wouldn't defrag enought to make a difference so I had to move
my
> focus to C: drive.
> Still no luck.
> I found an older version of w2k on c: drive and removed it.
> Defraged with heaps better oucome with diskkeeper.
> C: drive then had 4.5 gig free space
> Moved backup to C: drive (750 meg)
> and created new table on C: drive 1 k - (3.7 gig free on c: drive)
> Restored successfully.
> now have 3 gig free space
> Could have been just the free space restrictions.
> Difference between 3.1 failure and 4.5 success.
> Anyone know the formula?
> Perhaps 3gig / .75 gig failure = 4 times
> and 4.5 gig / .75 gig success = 6 times
> Thanks,
> baz
>
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:#V7#YyXXEHA.712@.TK2MSFTNGP11.phx.gbl...
> > Hi Peter,
> > Thanks for the reply.
> >
> > You have to have a database already setup on your server to restore
> to.
> >
> > So my database was only 1 k .
> > Ten after the failed attempt it is was 750megs.
> >
> > --
> >
> >
> > Had another look thru google.
> >
> > Looks like some others were having the same prob.
> >
> > Theirs turned out to be a severely defragmented hard drive.
> >
> > I've had a look thru mine with DiskKeeper.
> >
> > Mine is also severely defragmented as well.
> >
> > I've been defraggin all day but I can't get DiskKeeper to continue
> defraggin
> > on its own
> > I have to keep starting it and it only defrage 50 frags at a time? Who
> > knows ...
> >
> > I'll update a followup when I have some news...
> >
> >
>

Recovering (local) server and Restoring a Dabase from a clients backup

Hi all,
I'm running sql server 2000.
I've a client who has given me a large database to develope against.
I don't have a (local) server anymore. Can't remember why.
Whats the easiest way to recover (local) - I'm happy to reinstall and start
from a fresh (local).
Also, it looks as though the client has backed up their db.
Am I able to restore to my (local) from their backup?
Thanks,
bazYes you can restore it. You don't need to restore it locally unless you
want to. I would just place the backup some place where your development
server can see it, and then use EM to restore from the database backup.
Make sure you type in the name of the database you want to create from the
restore, so you don't overlay some other database.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> Hi all,
> I'm running sql server 2000.
> I've a client who has given me a large database to develope against.
> I don't have a (local) server anymore. Can't remember why.
> Whats the easiest way to recover (local) - I'm happy to reinstall and
start
> from a fresh (local).
> Also, it looks as though the client has backed up their db.
> Am I able to restore to my (local) from their backup?
> Thanks,
> baz
>
>|||Hi Greg,
Thanks for the quick reply.
Thats great news.
I'm trying to imulate the client setup as closely as possible.
I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
So, I do want a (local) server.
Anyone have any ideas on how to reinstall or recover the (local) server?
I reinstalled sql server last week but the (local) didn't re-appear.
And it looks like I have to have a database name already there to be able to
recover to it.
Any suggestions?
"Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
> Yes you can restore it. You don't need to restore it locally unless you
> want to. I would just place the backup some place where your development
> server can see it, and then use EM to restore from the database backup.
> Make sure you type in the name of the database you want to create from the
> restore, so you don't overlay some other database.
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:ev7qjfVXEHA.2964@.TK2MSFTNGP09.phx.gbl...
> start
>|||Attempting to sort out the Database name.
Just added a new database with the same name as the clients.
And used the All Task | Restore Database.
3.5 gigs available on the H: drive where I have the backed up database.
H: is where the .mdf resides as well.
3.1 gigs available of the c: drive
The backup itself is 734 megs.
All drives are NTFS
I'm getting this error:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Modify File encountered operating system error 112(There is not enought
space on the disk.) while attempting to expand the physical file.
Could not adjust the space allocation for file 'x-Log'.
Restore Datbase is terminating abnormally.
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
> Hi Greg,
> Thanks for the quick reply.
> Thats great news.
> --
> I'm trying to imulate the client setup as closely as possible.
> I'm modifying legacy VB 6 with ODBC connections thru a DSN (yuck!)
> And running legacy Crystal Reports 8.5 thru the same DSN (yucker!)
> So, I do want a (local) server.
> Anyone have any ideas on how to reinstall or recover the (local) server?
> I reinstalled sql server last week but the (local) didn't re-appear.
>
> And it looks like I have to have a database name already there to be able
to
> recover to it.
> Any suggestions?
>
> "Gregory A. Larsen" <greg.larsen@.netzero.com> wrote in message
> news:#AuHurVXEHA.3972@.TK2MSFTNGP12.phx.gbl...
development[vbcol=seagreen]
the[vbcol=seagreen]
> ----
> --
> ----
> --
>|||Make sure you are restoring the data and log files to a valid drive on your
local server. When your customer made the backup, the paths where the data
files resided on the customer's server are also recorded. When you now
restore the backup, SQL Server will by default try to restore the files to
the same location. You may need to change these paths. Since you are using
Enterprise Manager, look in the Options tab in the Restore database dialog.
If using Query Analyzer, look up the RESTORE FILELISTONLY .. and RESTORE
DATABASE ... WITH MOVE ... syntax.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23mPKjQWXEHA.736@.TK2MSFTNGP10.phx.gbl...
> Attempting to sort out the Database name.
> Just added a new database with the same name as the clients.
> And used the All Task | Restore Database.
> 3.5 gigs available on the H: drive where I have the backed up database.
> H: is where the .mdf resides as well.
> 3.1 gigs available of the c: drive
> The backup itself is 734 megs.
> All drives are NTFS
> I'm getting this error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Modify File encountered operating system error 112(There is not enought
> space on the disk.) while attempting to expand the physical file.
> Could not adjust the space allocation for file 'x-Log'.
> Restore Datbase is terminating abnormally.
> Thanks,
> baz
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:uvMji9VXEHA.2572@.TK2MSFTNGP11.phx.gbl...
able[vbcol=seagreen]
> to
you[vbcol=seagreen]
> development
backup.[vbcol=seagreen]
> the
> ----
> ----
and[vbcol=seagreen]
>|||Hi Peter,
Thanks for the reply.
You have to have a database already setup on your server to restore to.
So my database was only 1 k .
Ten after the failed attempt it is was 750megs.
Had another look thru google.
Looks like some others were having the same prob.
Theirs turned out to be a severely defragmented hard drive.
I've had a look thru mine with DiskKeeper.
Mine is also severely defragmented as well.
I've been defraggin all day but I can't get DiskKeeper to continue defraggin
on its own
I have to keep starting it and it only defrage 50 frags at a time? Who
knows ...
I'll update a followup when I have some news...|||Ok I've done it.
DiskKeeper wouldn't defrag enought to make a difference so I had to move my
focus to C: drive.
Still no luck.
I found an older version of w2k on c: drive and removed it.
Defraged with heaps better oucome with diskkeeper.
C: drive then had 4.5 gig free space
Moved backup to C: drive (750 meg)
and created new table on C: drive 1 k - (3.7 gig free on c: drive)
Restored successfully.
now have 3 gig free space
Could have been just the free space restrictions.
Difference between 3.1 failure and 4.5 success.
Anyone know the formula?
Perhaps 3gig / .75 gig failure = 4 times
and 4.5 gig / .75 gig success = 6 times
Thanks,
baz
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:#V7#YyXXEHA.712@.TK2MSFTNGP11.phx.gbl...
> Hi Peter,
> Thanks for the reply.
> You have to have a database already setup on your server to restore
to.
> So my database was only 1 k .
> Ten after the failed attempt it is was 750megs.
> --
>
> Had another look thru google.
> Looks like some others were having the same prob.
> Theirs turned out to be a severely defragmented hard drive.
> I've had a look thru mine with DiskKeeper.
> Mine is also severely defragmented as well.
> I've been defraggin all day but I can't get DiskKeeper to continue
defraggin
> on its own
> I have to keep starting it and it only defrage 50 frags at a time? Who
> knows ...
> I'll update a followup when I have some news...
>|||Don't know if there is such a formula, but it's sure something to keep in
mind. Thx for the update.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backup files? Try MiniSQLBackup
"Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
news:%23ODumxuXEHA.3944@.tk2msftngp13.phx.gbl...
> Ok I've done it.
> DiskKeeper wouldn't defrag enought to make a difference so I had to move
my
> focus to C: drive.
> Still no luck.
> I found an older version of w2k on c: drive and removed it.
> Defraged with heaps better oucome with diskkeeper.
> C: drive then had 4.5 gig free space
> Moved backup to C: drive (750 meg)
> and created new table on C: drive 1 k - (3.7 gig free on c: drive)
> Restored successfully.
> now have 3 gig free space
> Could have been just the free space restrictions.
> Difference between 3.1 failure and 4.5 success.
> Anyone know the formula?
> Perhaps 3gig / .75 gig failure = 4 times
> and 4.5 gig / .75 gig success = 6 times
> Thanks,
> baz
>
> "Barry G. Sumpter" <barrysum@.bigpond.net.au> wrote in message
> news:#V7#YyXXEHA.712@.TK2MSFTNGP11.phx.gbl...
> to.
> defraggin
>sql