Friday, March 23, 2012
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
Wednesday, March 21, 2012
I want to change this license option to per processor
I have done installation of SQL Server 2000 Standard edition with
licensing option as per seat (no. of seats 100). By mistake I had
choosen this option. Now I want to change this license option to per
processor (no. of processors 4).
Pls advice me is there any way to change this license option without
re-installation of SQL Server.
Karan
http://www.tkdinesh.com/faq/ans/license.html
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
sql
I want to change this license option to per processor
I have done installation of SQL Server 2000 Standard edition with
licensing option as per seat (no. of seats 100). By mistake I had
choosen this option. Now I want to change this license option to per
processor (no. of processors 4).
Pls advice me is there any way to change this license option without
re-installation of SQL Server.
Karanhttp://www.tkdinesh.com/faq/ans/license.html
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
I want to change this license option to per processor
I have done installation of SQL Server 2000 Standard edition with
licensing option as per seat (no. of seats 100). By mistake I had
choosen this option. Now I want to change this license option to per
processor (no. of processors 4).
Pls advice me is there any way to change this license option without
re-installation of SQL Server.
Karanhttp://www.tkdinesh.com/faq/ans/license.html
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
Monday, March 12, 2012
I ran a update quey by mistake
With out any BEGIN Transaction statement , i ran a update query.
I had to update just one record using the "Where field='abc'"
But i happened to miss that. Is there any chance of recovery? can i use the transaction logs to bring back the records before the update?
A quick answer is appreciated.
Sahel
Hi Sahel.
No way to get it back directly using native Sql tools/operations without performing some restore type operations.
Best way may be, if you have a standard backup structure in place, take a log backup immediately, then restore a copy of your database side-by-side with the existing db (using a different db name), and restore logs up to the point in time right before you ran the update statement (see the STOPAT option of the RESTORE LOG statement), then update the existing table with the values that exist in the table(s) from the restored database.
There are some 3rd party applications that you could consider researching and using, although these aren't a supported solution generally speaking, so be sure to clarify/understand that before using them (Lumigent Log Explorer is one for example).
HTH