Friday, March 30, 2012
I'd changed the server name, sql server can't start
can not start now, how can I restore the config? I don't want to reinstall
the sql server, thanks.Hi Tigershome,
To solve this, register your server again. Enter Enterprise Manager,
right-click on your SQL Server Group, then select New SQL Server
Registration... Follow the wizard and when it asks you for the server, type
the name of your new Windows 2K server. Continue and finish the wizard, and
your SQL Server will be up and running. If not, please post again.
Jerome Smith
"tigershome" <tigershome@.etang.com> wrote in message
news:OlLC7FZqDHA.2488@.TK2MSFTNGP12.phx.gbl...
> hi, I have changed the host name of windows 2K server , then sql server
2000
> can not start now, how can I restore the config? I don't want to reinstall
> the sql server, thanks.
>
>
Wednesday, March 28, 2012
I/O error on backup or restore restart-checkpoint file
"I/O error on backup or restore restart-checkpoint
file 'E:\Program Files\Microsoft SQL
Server\MSSQL\backup\Domain1.ckp'. Operating system error 3
(error not found). The statement is proceeding but is non-
restartable."
I get an error code 18272 (cant find it in BOL).
Note: Domain1 is the name of a specific database on my
server.
The directory 'E:\Program Files\Microsoft SQL
Server\MSSQL\backup' have been deleted so it is no wonder
that it can't either find nor create a file in that
directory.
The error was raised during a restore of the Domain1
database (the restore completed successfuly). I have a job
that kills every connection to the Domain1 database
(except it's own connection) for the database to be
restorable.
What setting must be set for SQL Server not to use this
directory for this purpose?
Note: backups (both data og log) are written just fine to
another directory.
Yours truly
Jakob Pedersen"Jakob Pedersen" <anonymous@.discussions.microsoft.com> wrote in message
news:171201c3e051$27d725d0$a301280a@.phx.gbl...
quote:
> Does any of you know what this is about :
> "I/O error on backup or restore restart-checkpoint
> file 'E:\Program Files\Microsoft SQL
> Server\MSSQL\backup\Domain1.ckp'. Operating system error 3
> (error not found). The statement is proceeding but is non-
> restartable."
> I get an error code 18272 (cant find it in BOL).
> Note: Domain1 is the name of a specific database on my
> server.
> The directory 'E:\Program Files\Microsoft SQL
> Server\MSSQL\backup' have been deleted so it is no wonder
> that it can't either find nor create a file in that
> directory.
> The error was raised during a restore of the Domain1
> database (the restore completed successfuly). I have a job
> that kills every connection to the Domain1 database
> (except it's own connection) for the database to be
> restorable.
Are you sure the restore was successful? It sounds like something did not
work quite right... do you still have the syntax you used for the restore?
quote:
> What setting must be set for SQL Server not to use this
> directory for this purpose?
It really depends on how you performed the restore here...
quote:
> Note: backups (both data og log) are written just fine to
> another directory.
During the restore? I'm not sure what you mean here.
Steve|||> "Jakob Pedersen" <anonymous@.discussions.microsoft.com> wrote in message
quote:
> news:171201c3e051$27d725d0$a301280a@.phx.gbl...
>
Are you sure the restore was successful? It sounds like something did not
work quite right... do you still have the syntax you used for the restore?
quote:
>
It really depends on how you performed the restore here...
[QUOTE]
During the restore? I'm not sure what you mean here.
Steve
[QUOTE]
>
Monday, March 26, 2012
I/O error (bad page id)
(sp_attach_db) and it won't restore from a backup file.
So we have the Mdf and Ldf files and a backup file but
since we detached, we can't seem to get the data on-line
again to do anything.
Any attempts to repair the database with CHECKDB results
in consistency errors. The database can be backed up but
not restored from a recent database backup. We tried to
recreate the database by using Copy Database Wizard and
DTS both with no success because of an I/O error. Trying
to query tables sometimes worked and other times didn't.
Finally, the database was detached and ended any attempts
to re-attach thus far.
Server: Msg 7995, Level 16, State 1, Line 1
Database 'woodsch0304' consistency errors in sysobjects,
sysindexes, syscolumns, or systypes prevent further
CHECKDB processing.
Not giving up yet...If the database has any value to you, it is time to open a call to MS PSS. I
think the cost is still $249.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> We can't get the database restored. It won't reattach
> (sp_attach_db) and it won't restore from a backup file.
> So we have the Mdf and Ldf files and a backup file but
> since we detached, we can't seem to get the data on-line
> again to do anything.
> Any attempts to repair the database with CHECKDB results
> in consistency errors. The database can be backed up but
> not restored from a recent database backup. We tried to
> recreate the database by using Copy Database Wizard and
> DTS both with no success because of an I/O error. Trying
> to query tables sometimes worked and other times didn't.
> Finally, the database was detached and ended any attempts
> to re-attach thus far.
> Server: Msg 7995, Level 16, State 1, Line 1
> Database 'woodsch0304' consistency errors in sysobjects,
> sysindexes, syscolumns, or systypes prevent further
> CHECKDB processing.
>
> Not giving up yet...
>|||You've lost a page in one of the critical (for CHECKDB and database use)
system tables so you're in danger of losing your database. I concur with
Wayne's suggestion - PSS is your best bet.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eGoGOWkJEHA.624@.TK2MSFTNGP11.phx.gbl...
> If the database has any value to you, it is time to open a call to MS PSS.
I
> think the cost is still $249.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
> news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
>
I/O error (bad page id)
(sp_attach_db) and it won't restore from a backup file.
So we have the Mdf and Ldf files and a backup file but
since we detached, we can't seem to get the data on-line
again to do anything.
Any attempts to repair the database with CHECKDB results
in consistency errors. The database can be backed up but
not restored from a recent database backup. We tried to
recreate the database by using Copy Database Wizard and
DTS both with no success because of an I/O error. Trying
to query tables sometimes worked and other times didn't.
Finally, the database was detached and ended any attempts
to re-attach thus far.
Server: Msg 7995, Level 16, State 1, Line 1
Database 'woodsch0304' consistency errors in sysobjects,
sysindexes, syscolumns, or systypes prevent further
CHECKDB processing.
Not giving up yet...
If the database has any value to you, it is time to open a call to MS PSS. I
think the cost is still $249.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> We can't get the database restored. It won't reattach
> (sp_attach_db) and it won't restore from a backup file.
> So we have the Mdf and Ldf files and a backup file but
> since we detached, we can't seem to get the data on-line
> again to do anything.
> Any attempts to repair the database with CHECKDB results
> in consistency errors. The database can be backed up but
> not restored from a recent database backup. We tried to
> recreate the database by using Copy Database Wizard and
> DTS both with no success because of an I/O error. Trying
> to query tables sometimes worked and other times didn't.
> Finally, the database was detached and ended any attempts
> to re-attach thus far.
> Server: Msg 7995, Level 16, State 1, Line 1
> Database 'woodsch0304' consistency errors in sysobjects,
> sysindexes, syscolumns, or systypes prevent further
> CHECKDB processing.
>
> Not giving up yet...
>
|||You've lost a page in one of the critical (for CHECKDB and database use)
system tables so you're in danger of losing your database. I concur with
Wayne's suggestion - PSS is your best bet.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eGoGOWkJEHA.624@.TK2MSFTNGP11.phx.gbl...
> If the database has any value to you, it is time to open a call to MS PSS.
I
> think the cost is still $249.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
> news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
>
I/O error (bad page id)
(sp_attach_db) and it won't restore from a backup file.
So we have the Mdf and Ldf files and a backup file but
since we detached, we can't seem to get the data on-line
again to do anything.
Any attempts to repair the database with CHECKDB results
in consistency errors. The database can be backed up but
not restored from a recent database backup. We tried to
recreate the database by using Copy Database Wizard and
DTS both with no success because of an I/O error. Trying
to query tables sometimes worked and other times didn't.
Finally, the database was detached and ended any attempts
to re-attach thus far.
Server: Msg 7995, Level 16, State 1, Line 1
Database 'woodsch0304' consistency errors in sysobjects,
sysindexes, syscolumns, or systypes prevent further
CHECKDB processing.
Not giving up yet...If the database has any value to you, it is time to open a call to MS PSS. I
think the cost is still $249.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> We can't get the database restored. It won't reattach
> (sp_attach_db) and it won't restore from a backup file.
> So we have the Mdf and Ldf files and a backup file but
> since we detached, we can't seem to get the data on-line
> again to do anything.
> Any attempts to repair the database with CHECKDB results
> in consistency errors. The database can be backed up but
> not restored from a recent database backup. We tried to
> recreate the database by using Copy Database Wizard and
> DTS both with no success because of an I/O error. Trying
> to query tables sometimes worked and other times didn't.
> Finally, the database was detached and ended any attempts
> to re-attach thus far.
> Server: Msg 7995, Level 16, State 1, Line 1
> Database 'woodsch0304' consistency errors in sysobjects,
> sysindexes, syscolumns, or systypes prevent further
> CHECKDB processing.
>
> Not giving up yet...
>|||You've lost a page in one of the critical (for CHECKDB and database use)
system tables so you're in danger of losing your database. I concur with
Wayne's suggestion - PSS is your best bet.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eGoGOWkJEHA.624@.TK2MSFTNGP11.phx.gbl...
> If the database has any value to you, it is time to open a call to MS PSS.
I
> think the cost is still $249.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
> news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> > We can't get the database restored. It won't reattach
> > (sp_attach_db) and it won't restore from a backup file.
> >
> > So we have the Mdf and Ldf files and a backup file but
> > since we detached, we can't seem to get the data on-line
> > again to do anything.
> >
> > Any attempts to repair the database with CHECKDB results
> > in consistency errors. The database can be backed up but
> > not restored from a recent database backup. We tried to
> > recreate the database by using Copy Database Wizard and
> > DTS both with no success because of an I/O error. Trying
> > to query tables sometimes worked and other times didn't.
> >
> > Finally, the database was detached and ended any attempts
> > to re-attach thus far.
> >
> > Server: Msg 7995, Level 16, State 1, Line 1
> >
> > Database 'woodsch0304' consistency errors in sysobjects,
> > sysindexes, syscolumns, or systypes prevent further
> > CHECKDB processing.
> >
> >
> > Not giving up yet...
> >
>
Friday, March 23, 2012
I want to revert back to original state of database before i performed restore database
i am in great trouble. I want to revert back to original state of
database before i performed restore database on my sql server 2K
Database. Accidently i didn't take backup of my Database and i did
restore, so is there any way to get the original state back of my
Database?
Any suggestion will be highly appriciated.
Regards,
S. Domadia."san" <shdomadia@.gmail.comwrote in message
news:1163592758.514890.277030@.h48g2000cwc.googlegr oups.com...
Quote:
Originally Posted by
Hello,
i am in great trouble. I want to revert back to original state of
database before i performed restore database on my sql server 2K
Database. Accidently i didn't take backup of my Database and i did
restore, so is there any way to get the original state back of my
Database?
>
If I understand you correctly, no.
You restored a backup over a copy of your database?
That completely overwrites it.
Quote:
Originally Posted by
Any suggestion will be highly appriciated.
>
>
Regards,
S. Domadia.
>
new files during the restore (e.g. backup was from a different server) and
the original deleted database files still exist on the drive. It's a long
shot but an undelete utility might allow you go recover those.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"san" <shdomadia@.gmail.comwrote in message
news:1163592758.514890.277030@.h48g2000cwc.googlegr oups.com...
Quote:
Originally Posted by
Hello,
i am in great trouble. I want to revert back to original state of
database before i performed restore database on my sql server 2K
Database. Accidently i didn't take backup of my Database and i did
restore, so is there any way to get the original state back of my
Database?
>
Any suggestion will be highly appriciated.
>
>
Regards,
S. Domadia.
>
I want to restore a database but it show me a mistake
Microsoft SQL-DMO 9 (ODBC SQLState: 42000)
Tha backup set holds a backup of a database other than the existing 'ACCESSCONTROL' database Backup or Restore operation terminating abnormally
What Can I Do for to resolve this error?
The SqlServer version 7.0The backup that you are restoring is of a different databse to the one =you are restoring, thus the error you are getting is a warning that =youwill be overwriting an existing database wich you may not intend to =do. The RESTORE SQl statement has an option WITH REPLACE, which =overrides this warning so if you really want to do what you are asking =it to do adding the equivalent optionshould fix your problem. If you =have yoiur own app using SQl DMO, then there should be an equivalent =option within DMO.
Mike John
"Lorena" <Lorena@.discussions.microsoft.com> wrote in message =news:0CC8EAC8-8200-47B0-9D8A-F3E5743F9837@.microsoft.com...
> I need restore a database but appears the nex error
> Microsoft SQL-DMO 9 (ODBC SQLState: 42000)
> Tha backup set holds a backup of a database other than the existing ='ACCESSCONTROL' database Backup or Restore operation terminating =abnormally
> What Can I Do for to resolve this error?
> The SqlServer version 7.0sql
I want to restore a database but it show me a mistake
Microsoft SQL-DMO 9 (ODBC SQLState: 42000)
Tha backup set holds a backup of a database other than the existing 'ACCESSCONTROL' database Backup or Restore operation terminating abnormally
What Can I Do for to resolve this error?
The SqlServer version 7.0
The backup that you are restoring is of a different databse to the one =
you are restoring, thus the error you are getting is a warning that =
youwill be overwriting an existing database wich you may not intend to =
do. The RESTORE SQl statement has an option WITH REPLACE, which =
overrides this warning so if you really want to do what you are asking =
it to do adding the equivalent optionshould fix your problem. If you =
have yoiur own app using SQl DMO, then there should be an equivalent =
option within DMO.
Mike John
"Lorena" <Lorena@.discussions.microsoft.com> wrote in message =
news:0CC8EAC8-8200-47B0-9D8A-F3E5743F9837@.microsoft.com...
> I need restore a database but appears the nex error
> Microsoft SQL-DMO 9 (ODBC SQLState: 42000)
> Tha backup set holds a backup of a database other than the existing =
'ACCESSCONTROL' database Backup or Restore operation terminating =
abnormally
> What Can I Do for to resolve this error?
> The SqlServer version 7.0
I want to restore a database but it show me a mistake
Microsoft SQL-DMO 9 (ODBC SQLState: 42000)
Tha backup set holds a backup of a database other than the existing 'ACCESSC
ONTROL' database Backup or Restore operation terminating abnormally
What Can I Do for to resolve this error?
The SqlServer version 7.0The backup that you are restoring is of a different databse to the one =
you are restoring, thus the error you are getting is a warning that =
youwill be overwriting an existing database wich you may not intend to =
do. The RESTORE SQl statement has an option WITH REPLACE, which =
overrides this warning so if you really want to do what you are asking =
it to do adding the equivalent optionshould fix your problem. If you =
have yoiur own app using SQl DMO, then there should be an equivalent =
option within DMO.
Mike John
"Lorena" <Lorena@.discussions.microsoft.com> wrote in message =
news:0CC8EAC8-8200-47B0-9D8A-F3E5743F9837@.microsoft.com...
> I need restore a database but appears the nex error
> Microsoft SQL-DMO 9 (ODBC SQLState: 42000)
> Tha backup set holds a backup of a database other than the existing =
'ACCESSCONTROL' database Backup or Restore operation terminating =
abnormally
> What Can I Do for to resolve this error?
> The SqlServer version 7.0