Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Friday, March 30, 2012

Restored Database/Diagrams Support/SQL-Server 2005

Hello,

I have restored a database from SQL-server 2000 into SQL-server 2005 and
when I try to install diagram support, I receive this error:

TITLE: Microsoft SQL Server Management Studio
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.

Section 5.8.1 of the SQL 2005 Readme file says:
The installation of these support objects can fail on a database that has
been attached or restored from another instance of SQL Server. This can occur
when the database owner name (stored in the database) is not a valid logon
for the instance of SQL Server the database is being attached or restored to.

Changing the owner with the line below did not solve the problem:
ALTER AUTHORIZATION ON DATABASE::databaseTest TO userTest

Can anyone help me with this issue?

Thanks
/Ershad

you're missing just a few steps...

ALTER AUTHORIZATION ON DATABASE::[databaseTest] TO userTest
go
use [databaseTest]
go
EXECUTE AS USER = N'dbo' REVERT
go

|||You answer was very helpful. Thank you very much! I only nedded to execute the following before I could run you statements

EXEC sp_dbcmptlevel 'databaseTest', '90';

|||Just in case anyone else experiences the same problem as I did I'll add one more comment. If your login is a domain account and you are working offline you may get this message until you connect to the domain.|||

Yeah!

It really works! but can I know why?

|||

It appears that the database must be converted to the compatibility level 90 (2005).. I tried all the other recommended commands, while retaining the SQL2000 compatibility level, and it would not work.

I will usually keep a dev data base at the compatibility level of the server it is hosted on, not automatically convert it to the level of my dev machine, but it looks like this is not going to be possible.. Someone please correct me if I am wrong as I would like to be able to continue doing this..

|||

????

?? ???????? ??? ??????.

??? ?? ????? ??????

|||

"Clint" reports an alternative in a thread on this topic at http://geekswithblogs.net/takenote/archive/2006/02/06/68381.aspx:

Actually, you can just go to the database properties, go to the Options page, and change the compatibility to SQL Server 2005.

This seems to have worked for me.

Either way, be advised that this change is not trouble-free for everyone: in the same thread, Harry Chou recommends a SQL Server 2005 Books Online topic that covers a variety of possible incompatibilities between SQL Server 2005 and previous versions: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/508c686d-2bd4-41ba-8602-48ebca266659.htm. These incompatibilities would become issues in a database after one of these approaches is used to make it compatible with SQL Server 2005.

I don't know if the Upgrade Wizard checks for these incompatibilities.

sql

Restored Database/Diagrams Support/SQL-Server 2005

Hello,

I have restored a database from SQL-server 2000 into SQL-server 2005 and
when I try to install diagram support, I receive this error:

TITLE: Microsoft SQL Server Management Studio
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.

Section 5.8.1 of the SQL 2005 Readme file says:
The installation of these support objects can fail on a database that has
been attached or restored from another instance of SQL Server. This can occur
when the database owner name (stored in the database) is not a valid logon
for the instance of SQL Server the database is being attached or restored to.

Changing the owner with the line below did not solve the problem:
ALTER AUTHORIZATION ON DATABASE::databaseTest TO userTest

Can anyone help me with this issue?

Thanks
/Ershad

you're missing just a few steps...

ALTER AUTHORIZATION ON DATABASE::[databaseTest] TO userTest
go
use [databaseTest]
go
EXECUTE AS USER = N'dbo' REVERT
go

|||You answer was very helpful. Thank you very much! I only nedded to execute the following before I could run you statements

EXEC sp_dbcmptlevel 'databaseTest', '90';

|||Just in case anyone else experiences the same problem as I did I'll add one more comment. If your login is a domain account and you are working offline you may get this message until you connect to the domain.|||

Yeah!

It really works! but can I know why?

|||

It appears that the database must be converted to the compatibility level 90 (2005).. I tried all the other recommended commands, while retaining the SQL2000 compatibility level, and it would not work.

I will usually keep a dev data base at the compatibility level of the server it is hosted on, not automatically convert it to the level of my dev machine, but it looks like this is not going to be possible.. Someone please correct me if I am wrong as I would like to be able to continue doing this..

|||

????

?? ???????? ??? ??????.

??? ?? ????? ??????

|||

"Clint" reports an alternative in a thread on this topic at http://geekswithblogs.net/takenote/archive/2006/02/06/68381.aspx:

Actually, you can just go to the database properties, go to the Options page, and change the compatibility to SQL Server 2005.

This seems to have worked for me.

Either way, be advised that this change is not trouble-free for everyone: in the same thread, Harry Chou recommends a SQL Server 2005 Books Online topic that covers a variety of possible incompatibilities between SQL Server 2005 and previous versions: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/508c686d-2bd4-41ba-8602-48ebca266659.htm. These incompatibilities would become issues in a database after one of these approaches is used to make it compatible with SQL Server 2005.

I don't know if the Upgrade Wizard checks for these incompatibilities.

Restored Database/Diagrams Support/SQL-Server 2005

Hello,

I have restored a database from SQL-server 2000 into SQL-server 2005 and
when I try to install diagram support, I receive this error:

TITLE: Microsoft SQL Server Management Studio
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.

Section 5.8.1 of the SQL 2005 Readme file says:
The installation of these support objects can fail on a database that has
been attached or restored from another instance of SQL Server. This can occur
when the database owner name (stored in the database) is not a valid logon
for the instance of SQL Server the database is being attached or restored to.

Changing the owner with the line below did not solve the problem:
ALTER AUTHORIZATION ON DATABASE::databaseTest TO userTest

Can anyone help me with this issue?

Thanks
/Ershad

you're missing just a few steps...

ALTER AUTHORIZATION ON DATABASE::[databaseTest] TO userTest
go
use [databaseTest]
go
EXECUTE AS USER = N'dbo' REVERT
go

|||You answer was very helpful. Thank you very much! I only nedded to execute the following before I could run you statements

EXEC sp_dbcmptlevel 'databaseTest', '90';

|||Just in case anyone else experiences the same problem as I did I'll add one more comment. If your login is a domain account and you are working offline you may get this message until you connect to the domain.|||

Yeah!

It really works! but can I know why?

|||

It appears that the database must be converted to the compatibility level 90 (2005).. I tried all the other recommended commands, while retaining the SQL2000 compatibility level, and it would not work.

I will usually keep a dev data base at the compatibility level of the server it is hosted on, not automatically convert it to the level of my dev machine, but it looks like this is not going to be possible.. Someone please correct me if I am wrong as I would like to be able to continue doing this..

|||

????

?? ???????? ??? ??????.

??? ?? ????? ??????

|||

"Clint" reports an alternative in a thread on this topic at http://geekswithblogs.net/takenote/archive/2006/02/06/68381.aspx:

Actually, you can just go to the database properties, go to the Options page, and change the compatibility to SQL Server 2005.

This seems to have worked for me.

Either way, be advised that this change is not trouble-free for everyone: in the same thread, Harry Chou recommends a SQL Server 2005 Books Online topic that covers a variety of possible incompatibilities between SQL Server 2005 and previous versions: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/508c686d-2bd4-41ba-8602-48ebca266659.htm. These incompatibilities would become issues in a database after one of these approaches is used to make it compatible with SQL Server 2005.

I don't know if the Upgrade Wizard checks for these incompatibilities.

Restored Database/Diagrams Support/SQL-Server 2005

Hello,

I have restored a database from SQL-server 2000 into SQL-server 2005 and
when I try to install diagram support, I receive this error:

TITLE: Microsoft SQL Server Management Studio
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.

Section 5.8.1 of the SQL 2005 Readme file says:
The installation of these support objects can fail on a database that has
been attached or restored from another instance of SQL Server. This can occur
when the database owner name (stored in the database) is not a valid logon
for the instance of SQL Server the database is being attached or restored to.

Changing the owner with the line below did not solve the problem:
ALTER AUTHORIZATION ON DATABASE::databaseTest TO userTest

Can anyone help me with this issue?

Thanks
/Ershad

you're missing just a few steps...

ALTER AUTHORIZATION ON DATABASE::[databaseTest] TO userTest
go
use [databaseTest]
go
EXECUTE AS USER = N'dbo' REVERT
go

|||You answer was very helpful. Thank you very much! I only nedded to execute the following before I could run you statements

EXEC sp_dbcmptlevel 'databaseTest', '90';

|||Just in case anyone else experiences the same problem as I did I'll add one more comment. If your login is a domain account and you are working offline you may get this message until you connect to the domain.|||

Yeah!

It really works! but can I know why?

|||

It appears that the database must be converted to the compatibility level 90 (2005).. I tried all the other recommended commands, while retaining the SQL2000 compatibility level, and it would not work.

I will usually keep a dev data base at the compatibility level of the server it is hosted on, not automatically convert it to the level of my dev machine, but it looks like this is not going to be possible.. Someone please correct me if I am wrong as I would like to be able to continue doing this..

|||

????

?? ???????? ??? ??????.

??? ?? ????? ??????

|||

"Clint" reports an alternative in a thread on this topic at http://geekswithblogs.net/takenote/archive/2006/02/06/68381.aspx:

Actually, you can just go to the database properties, go to the Options page, and change the compatibility to SQL Server 2005.

This seems to have worked for me.

Either way, be advised that this change is not trouble-free for everyone: in the same thread, Harry Chou recommends a SQL Server 2005 Books Online topic that covers a variety of possible incompatibilities between SQL Server 2005 and previous versions: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/508c686d-2bd4-41ba-8602-48ebca266659.htm. These incompatibilities would become issues in a database after one of these approaches is used to make it compatible with SQL Server 2005.

I don't know if the Upgrade Wizard checks for these incompatibilities.

Restored Database/Diagrams Support/SQL-Server 2005

Hello,

I have restored a database from SQL-server 2000 into SQL-server 2005 and
when I try to install diagram support, I receive this error:

TITLE: Microsoft SQL Server Management Studio
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.

Section 5.8.1 of the SQL 2005 Readme file says:
The installation of these support objects can fail on a database that has
been attached or restored from another instance of SQL Server. This can occur
when the database owner name (stored in the database) is not a valid logon
for the instance of SQL Server the database is being attached or restored to.

Changing the owner with the line below did not solve the problem:
ALTER AUTHORIZATION ON DATABASE::databaseTest TO userTest

Can anyone help me with this issue?

Thanks
/Ershad

you're missing just a few steps...

ALTER AUTHORIZATION ON DATABASE::[databaseTest] TO userTest
go
use [databaseTest]
go
EXECUTE AS USER = N'dbo' REVERT
go

|||You answer was very helpful. Thank you very much! I only nedded to execute the following before I could run you statements

EXEC sp_dbcmptlevel 'databaseTest', '90';

|||Just in case anyone else experiences the same problem as I did I'll add one more comment. If your login is a domain account and you are working offline you may get this message until you connect to the domain.|||

Yeah!

It really works! but can I know why?

|||

It appears that the database must be converted to the compatibility level 90 (2005).. I tried all the other recommended commands, while retaining the SQL2000 compatibility level, and it would not work.

I will usually keep a dev data base at the compatibility level of the server it is hosted on, not automatically convert it to the level of my dev machine, but it looks like this is not going to be possible.. Someone please correct me if I am wrong as I would like to be able to continue doing this..

|||

????

?? ???????? ??? ??????.

??? ?? ????? ??????

|||

"Clint" reports an alternative in a thread on this topic at http://geekswithblogs.net/takenote/archive/2006/02/06/68381.aspx:

Actually, you can just go to the database properties, go to the Options page, and change the compatibility to SQL Server 2005.

This seems to have worked for me.

Either way, be advised that this change is not trouble-free for everyone: in the same thread, Harry Chou recommends a SQL Server 2005 Books Online topic that covers a variety of possible incompatibilities between SQL Server 2005 and previous versions: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/508c686d-2bd4-41ba-8602-48ebca266659.htm. These incompatibilities would become issues in a database after one of these approaches is used to make it compatible with SQL Server 2005.

I don't know if the Upgrade Wizard checks for these incompatibilities.

restore: EXCEPTION_ACCESS_VIOLATION c0000005 (17052)

Because of a corrupt mainboard we tried to restore our SQL Server 7
databases to a new computer but get the same error for all backups we
try to restore:
---
ODBC: Nachr.-Nr. 0, Schweregrad 19, Status 1
SqlDumpExceptionHandler: Prozess 21 erzeugte eine schwere
Ausnahmebedingung c0000005 EXCEPTION_ACCESS_VIOLATION.Sql Server
beendet diesen Prozess.
---
The Windows event log shows an event ID 17052. What can be wrong?I check out www.eventid.net for this issue and found something about it and
wanted to share with you. Maybe you can find something useful.
From www.EventId.net
Adrian Grigorof (Last update 1/4/2005):
This appears to be a generic event that can be recorded by the MS SQL Server
service for a wide range of problems. See the information for various errors
(ordered by the error number).
Error: 0, Description: SqlDumpExceptionHandler: Process 10 generated fatal
exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating
this process. - This type of error indicates a bug in one of the MS SQL
Server binaries. Installation of the latest service pack recommended. If
that does not fix it then call Microsoft Product support. Some newsgroup
postings suggest that this may occur due to lack of space on drive
containing the SQL logs
Event ID: 17052
Source MSSQLSERVER
Type Error
Description You do not have sufficient operating system permission to open
the SQLServerAgent status event.
Comments Adrian Grigorof (Last update 7/28/2004):
From a newsgroup post: "Installing SP3 or SP3a on MS SQL Server 2000
Enterprise Edition caused this problem in my case (MSSQLServer service is
running under different local user account than the SqlServerAgent service
and MSSQLServer is not given Administrator privileges). I see this buggy
behavior on various installations: W2K Advanced Server SP4 or W2K3. SP3 or
SP3a. Default instance or named instance. New freshly installed server or
old one. The only condition is that the MSSQLServer and SQLServerAgent
services run with different user accounts and the MSSQLServer
one does not have admin rights. Before SP3 installation everything runs OK.
What helps: Add MSSQLServer service account to Administrators group. OR Run
MSSQLServer and SQLServerAgent with the same account.
What doesn't help: Changing the services' user accounts using Enterprise
Manager. Add services' accounts to Power Users."
An answer from a MS engineer in a newsgroup post: "I suspect that the issue
is addressed in the cross-database ownership chain which uses in Microsoft
SQL Server Service Pack 3 (SP3). Based on my research, SP3 provides a new
security enhancement related option for configuring cross-database ownership
chaining; enable cross-database ownership chaining for all databases during
setup. With this new option, you can control whether or not you permit
cross-database ownership chaining. By default, this option is disabled.
Microsoft recommends that you use the default option, because it makes your
database server more secure.
However, database objects may have different owners. When an object such as
a view, a stored procedure, or a user-defined function references another
object, an ownership chain can be established. When the ownership chain is
unbroken, SQL Server checks permissions on the source object but not on the
target objects.
Therefore, it is recommended that you change the configuration of the
cross-database ownership chaining. You can reference the following
step-by-step article to perform such a change: M810474 (Cross-Database
Ownership Chaining Behavior Changes in SQL Server).
Additionally, I also suggest you running the MSSQLServer service with a
local account and
SQLServerAgent with Admin privilege to see if the jobs work fine. Otherwise,
it seems that you
should run these both services with the FULL privileges."
From a newsgroup post: "This is most likely a permissions issue. Make sure
the account SQLAgent starting under has permissions to:
- Replace A process level token
- Increase Quotas
- Logon as a service.
Books online states that the account needs to be a member of the local
admins group as well."
Anonymous (Last update 7/28/2004):
I got this error after I have created different accounts for sqlserver and
sqlagent service.
Ekrem Önsoy
"dentaku" <dentaku@.web.de> wrote in message
news:1189672135.231927.120740@.d55g2000hsg.googlegroups.com...
> Because of a corrupt mainboard we tried to restore our SQL Server 7
> databases to a new computer but get the same error for all backups we
> try to restore:
> ---
> ODBC: Nachr.-Nr. 0, Schweregrad 19, Status 1
> SqlDumpExceptionHandler: Prozess 21 erzeugte eine schwere
> Ausnahmebedingung c0000005 EXCEPTION_ACCESS_VIOLATION.Sql Server
> beendet diesen Prozess.
> ---
> The Windows event log shows an event ID 17052. What can be wrong?
>|||We have plenty of free disk and memory space (multiple GBs). We also
have the latest microsoft service packs and updates. And our DB user
is an admin (DBO rights didn't help either).
All restore verifyonly/filelistonly/headeronly requests returned no
error. But every time I try to restore the database (file) I get this
error and the sql error log files says
Bypassing recovery for database 'mine' because it is marked IN LOAD.
I can delete this database, and restore again, but with always the
same error.

Monday, March 26, 2012

Restore Tranaction log


I am trying to restore a Transaction Log in SQL Server 2000 in Full recovery status, However I was received the following error Message:
----------------------------------------
Error message: Exclusive access could not be obtained because the database is in use.
----------------------------------------
Also I changed the UserAccess database from MULTI_USER to SINGLE_USER, but still do not work and shows the same error message.
Please let me know, if you have any solution for this problem.


Thanks,

Try the link below to test drive Lumigent. Hope this helps.
http://www.lumigent.com/

Restore Tlog on SQL 6.5

Hello everyone,
I am trying to apply transaction log dumps to a database and it is
giving me the error:
Specified file 'X:\mssql\BACKUP\PrimoProd_tlog_amdump.DAT' is out of
sequence. Current time stamp is May 20 2004 8:31PM while dump was from
May 23 2004 7:41PM.
Here are the details: I restored the database with the full backup from
05/20/2004 9:00 pm. Now I am trying to apply the Tlogs that were backed
up starting 05/21/04 at 6:00 am. The Tlogs were backed up to a single
device. That is, the backup file primoprod_tlog_dump.dat has all the
tlog backups on it from the 05/21 am to about 05/23 pm. Therefore the
date stamp on that file is 05/23. This is what SQL 6.5 is complaining
about. I restored the database using a file that was backed up on 05/20
and now I am applying logs from a file which has a date stamp of 05/23
but this file does have the tlogs from 05/21 within it. What should I
do? I am specifying the correct tolog to apply i.e. from 05/21 am. The
very first tlog after the full backup.
Raziq.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Hi,
I can see 2 issues with your restore.
First issue.
--
The destination database you are trying to restore shoule be set to below
options
1. Read Only
2. no chkpt on recovery
How to set this options
sp_dboption dbname,'Read Only',True
go
sp_dboption dbname,'no chkpt on recovery',True
Second Issue
--
As you say "The Tlogs were backed up to a single device." - Did you mean all
the transaction logs are
appended to the same backup file". Then you cant load the transaction
directly.
Firt execute the below statement to get the Sequence details:-
load headeronly from disk='e:\mssql\backup\backup_file_name_with_extension'
(Change the directory based on yours)
The above command will give you the sequence details for each transaction
log backup
available inside the backup file
Some thing like:
Dumptype Database Striped Compressed Sequence
-- -- -- -- --
2 vanrpt 0 0 1
2 vanrpt 0 0 2
So while loading the transaction log backup in destination database you have
to specify FILE = @.filenumber
(File number is nothing but the sequence number provided by LOAD Headeronly
command)
How to load the transaction log
Load transaction dbname from disk='backupfile' with file=1
go
Load transaction dbname from disk='backupfile' with file=2
Note:
Before doing the Load set the database options mentioned in "First Issue"
Thanks
Hari
MCDBA
"Raziq Shekha" <raziq_shekha@.anadarko.com> wrote in message
news:O40suVbQEHA.964@.TK2MSFTNGP10.phx.gbl...
> Hello everyone,
> I am trying to apply transaction log dumps to a database and it is
> giving me the error:
> Specified file 'X:\mssql\BACKUP\PrimoProd_tlog_amdump.DAT' is out of
> sequence. Current time stamp is May 20 2004 8:31PM while dump was from
> May 23 2004 7:41PM.
> Here are the details: I restored the database with the full backup from
> 05/20/2004 9:00 pm. Now I am trying to apply the Tlogs that were backed
> up starting 05/21/04 at 6:00 am. The Tlogs were backed up to a single
> device. That is, the backup file primoprod_tlog_dump.dat has all the
> tlog backups on it from the 05/21 am to about 05/23 pm. Therefore the
> date stamp on that file is 05/23. This is what SQL 6.5 is complaining
> about. I restored the database using a file that was backed up on 05/20
> and now I am applying logs from a file which has a date stamp of 05/23
> but this file does have the tlogs from 05/21 within it. What should I
> do? I am specifying the correct tolog to apply i.e. from 05/21 am. The
> very first tlog after the full backup.
> Raziq.
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Wednesday, March 21, 2012

Restore sql 2000 database .bak file to sql 2005

I am trying to restore a sql 2000 .bak file to a sql 2005. Error I get
is "
Restore failed for Server" - The backup set holds a backup of a
database other than the existing 'db name here ' database.
(Microsoft.SqlServer.Smo)
Pleawse help
Add WITH REPLACE to your RESTORE DATABASE statement if you want to restore
from a backup file of a different database.
Linchi
"CW" <wallacec@.gmail.com> wrote in message
news:1139442397.257269.102990@.g44g2000cwa.googlegr oups.com...
>I am trying to restore a sql 2000 .bak file to a sql 2005. Error I get
> is "
> Restore failed for Server" - The backup set holds a backup of a
> database other than the existing 'db name here ' database.
> (Microsoft.SqlServer.Smo)
> Pleawse help
>
|||RESTORE DATABASE DB_NAME_TO_BE_RESTORED
FROM DISK = 'F:\backupfilename.bak'
WITH MOVE 'Logical_Name_Data' TO 'F:\MSSQL\DATA\Physical_Name_Data.mdf',
MOVE 'Logical_Data_Log' TO 'E:\MSSQL\LOG\Physical_Name_Log.ldf',
STATS = 1, REPLACE
GO
Thanks,
Sree
"Linchi Shea" wrote:

> Add WITH REPLACE to your RESTORE DATABASE statement if you want to restore
> from a backup file of a different database.
> Linchi
> "CW" <wallacec@.gmail.com> wrote in message
> news:1139442397.257269.102990@.g44g2000cwa.googlegr oups.com...
>
>

Restore sql 2000 database .bak file to sql 2005

I am trying to restore a sql 2000 .bak file to a sql 2005. Error I get
is "
Restore failed for Server" - The backup set holds a backup of a
database other than the existing 'db name here ' database.
(Microsoft.SqlServer.Smo)
Pleawse helpAdd WITH REPLACE to your RESTORE DATABASE statement if you want to restore
from a backup file of a different database.
Linchi
"CW" <wallacec@.gmail.com> wrote in message
news:1139442397.257269.102990@.g44g2000cwa.googlegroups.com...
>I am trying to restore a sql 2000 .bak file to a sql 2005. Error I get
> is "
> Restore failed for Server" - The backup set holds a backup of a
> database other than the existing 'db name here ' database.
> (Microsoft.SqlServer.Smo)
> Pleawse help
>|||RESTORE DATABASE DB_NAME_TO_BE_RESTORED
FROM DISK = 'F:\backupfilename.bak'
WITH MOVE 'Logical_Name_Data' TO 'F:\MSSQL\DATA\Physical_Name_Data.mdf',
MOVE 'Logical_Data_Log' TO 'E:\MSSQL\LOG\Physical_Name_Log.ldf',
STATS = 1, REPLACE
GO
Thanks,
Sree
"Linchi Shea" wrote:
> Add WITH REPLACE to your RESTORE DATABASE statement if you want to restore
> from a backup file of a different database.
> Linchi
> "CW" <wallacec@.gmail.com> wrote in message
> news:1139442397.257269.102990@.g44g2000cwa.googlegroups.com...
> >I am trying to restore a sql 2000 .bak file to a sql 2005. Error I get
> > is "
> > Restore failed for Server" - The backup set holds a backup of a
> > database other than the existing 'db name here ' database.
> > (Microsoft.SqlServer.Smo)
> > Pleawse help
> >
>
>sql

Restore sql 2000 database .bak file to sql 2005

I am trying to restore a sql 2000 .bak file to a sql 2005. Error I get
is "
Restore failed for Server" - The backup set holds a backup of a
database other than the existing 'db name here ' database.
(Microsoft.SqlServer.Smo)
Pleawse helpAdd WITH REPLACE to your RESTORE DATABASE statement if you want to restore
from a backup file of a different database.
Linchi
"CW" <wallacec@.gmail.com> wrote in message
news:1139442397.257269.102990@.g44g2000cwa.googlegroups.com...
>I am trying to restore a sql 2000 .bak file to a sql 2005. Error I get
> is "
> Restore failed for Server" - The backup set holds a backup of a
> database other than the existing 'db name here ' database.
> (Microsoft.SqlServer.Smo)
> Pleawse help
>|||RESTORE DATABASE DB_NAME_TO_BE_RESTORED
FROM DISK = 'F:\backupfilename.bak'
WITH MOVE 'Logical_Name_Data' TO 'F:\MSSQL\DATA\Physical_Name_Data.mdf',
MOVE 'Logical_Data_Log' TO 'E:\MSSQL\LOG\Physical_Name_Log.ldf',
STATS = 1, REPLACE
GO
Thanks,
Sree
"Linchi Shea" wrote:

> Add WITH REPLACE to your RESTORE DATABASE statement if you want to restore
> from a backup file of a different database.
> Linchi
> "CW" <wallacec@.gmail.com> wrote in message
> news:1139442397.257269.102990@.g44g2000cwa.googlegroups.com...
>
>

Tuesday, March 20, 2012

Restore question

While doing a reorganize on Friday, the drive filled up, and the operation
failed with an error. The database on the next full backup went from 1.5 gig
to 3 gig in size. (full backup occurs every 24 hours).
I have tran-logs created every hour and a full backup from the day before
(Thursday). Can I restore the Thursday backup and then restore all tran-logs
(Thursday, Friday, Saturday, Sunday, Monday, and Tuesday) and expect to have
all my data or can I only restore up to the point of my next full backup
(Saturday)?
Thank you
G.Hi,
Why do you need to restore the database? Because your current database is
still available. Based on your mail I feel that your
Backup file size has grown from 1.5 GB to 3 GB.
I feel that this growth is because of the Reorginization activity. I think
the backup file size can be solved by just shrinking the Log file.
How to shrink the log file:
1. Backup the Transaction log (Use Backup Log command)
2. Use dbcc shrink file to shrink the file
See the below link for shrinking the transaction log file.
http://support.microsoft.com/defaul...b;EN-US;q272318
Thanks
Hari
MCDBA
"Ric Griffy" <alakevue.at@.tampabay.rr.com> wrote in message
news:QA78c.333946$Po1.285683@.twister.tampabay.rr.com...
> While doing a reorganize on Friday, the drive filled up, and the operation
> failed with an error. The database on the next full backup went from 1.5
gig
> to 3 gig in size. (full backup occurs every 24 hours).
> I have tran-logs created every hour and a full backup from the day before
> (Thursday). Can I restore the Thursday backup and then restore all
tran-logs
> (Thursday, Friday, Saturday, Sunday, Monday, and Tuesday) and expect to
have
> all my data or can I only restore up to the point of my next full backup
> (Saturday)?
> Thank you
> G.
>
>|||I agree with Hari that nothing from your description indicates that you need
to do a restore.
To answer the direct question: Yes, you can skip restoring a database
backup. Performing a database backup does not break the chain of log
backups. This is one of the reasons why the log *is not* truncated when you
perform a database backup.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Ric Griffy" <alakevue.at@.tampabay.rr.com> wrote in message
news:QA78c.333946$Po1.285683@.twister.tampabay.rr.com...
> While doing a reorganize on Friday, the drive filled up, and the operation
> failed with an error. The database on the next full backup went from 1.5
gig
> to 3 gig in size. (full backup occurs every 24 hours).
> I have tran-logs created every hour and a full backup from the day before
> (Thursday). Can I restore the Thursday backup and then restore all
tran-logs
> (Thursday, Friday, Saturday, Sunday, Monday, and Tuesday) and expect to
have
> all my data or can I only restore up to the point of my next full backup
> (Saturday)?
> Thank you
> G.
>
>

Monday, March 12, 2012

Restore Problems

From time to time I receive the following error while
restoring:
"The log in this backup set terminates at LSNxxx, which
is too early to apply to the database. A more recent log
backup that includes LSNxxx can be restored."
I am not backing up any logs. This is my backup command:
BACKUP DATABASE [Order] TO DISK = N'C:\Program
Files\Microsoft SQL Server\MSSQL\BACKUP\Orderback' WITH
INIT , NOUNLOAD , NAME = N'Order backup', NOSKIP ,
STATS = 10, NOFORMAT
This is my restore:
restore database [order]
filegroup = 'primary', filegroup = 'ORDER1', filegroup
= 'ORDER2'
from disk='c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\Orderback'
with file=1,norecovery,partial,replace,
move 'order_data' to 'c:\program files\microsoft sql
server\mssql\data\order_data.mdf',
move 'order_data1' to 'c:\program files\microsoft sql
server\mssql\data\order_data1.ndf',
move 'order_data2' to 'c:\program files\microsoft sql
server\mssql\data\order_data2.ndf',
move 'order_log' to 'c:\program files\microsoft sql
server\mssql\data\order_log.ldf'
go
restore log [order]
from disk='c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\Orderback'
with file=1,recovery
goHi Paul.
I don't think you need that final restore log command - the full database
restore will fully restore the database and log entries in that file so I'm
wondering what you're expecting to get from that restore log command?
Regards,
Greg Linwood
SQL Server MVP
"Paul Offerle" <pofferle@.fmcconnell.com> wrote in message
news:664a01c4016a$6821c020$a001280a@.phx.gbl...
> From time to time I receive the following error while
> restoring:
> "The log in this backup set terminates at LSNxxx, which
> is too early to apply to the database. A more recent log
> backup that includes LSNxxx can be restored."
> I am not backing up any logs. This is my backup command:
> BACKUP DATABASE [Order] TO DISK = N'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\Orderback' WITH
> INIT , NOUNLOAD , NAME = N'Order backup', NOSKIP ,
> STATS = 10, NOFORMAT
> This is my restore:
> restore database [order]
> filegroup = 'primary', filegroup = 'ORDER1', filegroup
> = 'ORDER2'
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,norecovery,partial,replace,
> move 'order_data' to 'c:\program files\microsoft sql
> server\mssql\data\order_data.mdf',
> move 'order_data1' to 'c:\program files\microsoft sql
> server\mssql\data\order_data1.ndf',
> move 'order_data2' to 'c:\program files\microsoft sql
> server\mssql\data\order_data2.ndf',
> move 'order_log' to 'c:\program files\microsoft sql
> server\mssql\data\order_log.ldf'
> go
> restore log [order]
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,recovery
> go|||When I omit the restore log, I am unable to access the
database. Enterprise Manager displays "(loading)" next to
the database name.|||Paul
Although Greg said the restore database will "will fully restore the
database and log entries in that file", he meant it COULD do the full
restore, but only if you specify the keyword RECOVERY. The default is not to
run recovery, with the assumption that you will first be applying more logs.
Recovery needs to be run with the last thing you're restoring.
Use the recovery option on your RESTORE DATABASE command and you won't need
to restore any logs.
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
<anonymous@.discussions.microsoft.com> wrote in message
news:6cca01c401fd$90a802a0$a301280a@.phx.gbl...
> When I omit the restore log, I am unable to access the
> database. Enterprise Manager displays "(loading)" next to
> the database name.|||Try dropping the database before doing the restore.
I have found that doing filegroup restores using the REPLACE option creates
these type of errors.
Good Luck.
**********************************
"Paul Offerle" <pofferle@.fmcconnell.com> wrote in message
news:664a01c4016a$6821c020$a001280a@.phx.gbl...
> From time to time I receive the following error while
> restoring:
> "The log in this backup set terminates at LSNxxx, which
> is too early to apply to the database. A more recent log
> backup that includes LSNxxx can be restored."
> I am not backing up any logs. This is my backup command:
> BACKUP DATABASE [Order] TO DISK = N'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\Orderback' WITH
> INIT , NOUNLOAD , NAME = N'Order backup', NOSKIP ,
> STATS = 10, NOFORMAT
> This is my restore:
> restore database [order]
> filegroup = 'primary', filegroup = 'ORDER1', filegroup
> = 'ORDER2'
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,norecovery,partial,replace,
> move 'order_data' to 'c:\program files\microsoft sql
> server\mssql\data\order_data.mdf',
> move 'order_data1' to 'c:\program files\microsoft sql
> server\mssql\data\order_data1.ndf',
> move 'order_data2' to 'c:\program files\microsoft sql
> server\mssql\data\order_data2.ndf',
> move 'order_log' to 'c:\program files\microsoft sql
> server\mssql\data\order_log.ldf'
> go
> restore log [order]
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,recovery
> go|||ooops - I missed that the restore db didn't have recovery option..
Regards,
Greg Linwood
SQL Server MVP
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%238XCQEgAEHA.1420@.TK2MSFTNGP11.phx.gbl...
> Paul
> Although Greg said the restore database will "will fully restore the
> database and log entries in that file", he meant it COULD do the full
> restore, but only if you specify the keyword RECOVERY. The default is not
to
> run recovery, with the assumption that you will first be applying more
logs.
> Recovery needs to be run with the last thing you're restoring.
> Use the recovery option on your RESTORE DATABASE command and you won't
need
> to restore any logs.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:6cca01c401fd$90a802a0$a301280a@.phx.gbl...
>|||Thank you very much.

Restore Problems

From time to time I receive the following error while
restoring:
"The log in this backup set terminates at LSNxxx, which
is too early to apply to the database. A more recent log
backup that includes LSNxxx can be restored."
I am not backing up any logs. This is my backup command:
BACKUP DATABASE [Order] TO DISK = N'C:\Program
Files\Microsoft SQL Server\MSSQL\BACKUP\Orderback' WITH
INIT , NOUNLOAD , NAME = N'Order backup', NOSKIP ,
STATS = 10, NOFORMAT
This is my restore:
restore database [order]
filegroup = 'primary', filegroup = 'ORDER1', filegroup
= 'ORDER2'
from disk='c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\Orderback'
with file=1,norecovery,partial,replace,
move 'order_data' to 'c:\program files\microsoft sql
server\mssql\data\order_data.mdf',
move 'order_data1' to 'c:\program files\microsoft sql
server\mssql\data\order_data1.ndf',
move 'order_data2' to 'c:\program files\microsoft sql
server\mssql\data\order_data2.ndf',
move 'order_log' to 'c:\program files\microsoft sql
server\mssql\data\order_log.ldf'
go
restore log [order]
from disk='c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\Orderback'
with file=1,recovery
goHi Paul.
I don't think you need that final restore log command - the full database
restore will fully restore the database and log entries in that file so I'm
wondering what you're expecting to get from that restore log command?
Regards,
Greg Linwood
SQL Server MVP
"Paul Offerle" <pofferle@.fmcconnell.com> wrote in message
news:664a01c4016a$6821c020$a001280a@.phx.gbl...
> From time to time I receive the following error while
> restoring:
> "The log in this backup set terminates at LSNxxx, which
> is too early to apply to the database. A more recent log
> backup that includes LSNxxx can be restored."
> I am not backing up any logs. This is my backup command:
> BACKUP DATABASE [Order] TO DISK = N'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\Orderback' WITH
> INIT , NOUNLOAD , NAME = N'Order backup', NOSKIP ,
> STATS = 10, NOFORMAT
> This is my restore:
> restore database [order]
> filegroup = 'primary', filegroup = 'ORDER1', filegroup
> = 'ORDER2'
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,norecovery,partial,replace,
> move 'order_data' to 'c:\program files\microsoft sql
> server\mssql\data\order_data.mdf',
> move 'order_data1' to 'c:\program files\microsoft sql
> server\mssql\data\order_data1.ndf',
> move 'order_data2' to 'c:\program files\microsoft sql
> server\mssql\data\order_data2.ndf',
> move 'order_log' to 'c:\program files\microsoft sql
> server\mssql\data\order_log.ldf'
> go
> restore log [order]
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,recovery
> go|||When I omit the restore log, I am unable to access the
database. Enterprise Manager displays "(loading)" next to
the database name.|||Paul
Although Greg said the restore database will "will fully restore the
database and log entries in that file", he meant it COULD do the full
restore, but only if you specify the keyword RECOVERY. The default is not to
run recovery, with the assumption that you will first be applying more logs.
Recovery needs to be run with the last thing you're restoring.
Use the recovery option on your RESTORE DATABASE command and you won't need
to restore any logs.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
<anonymous@.discussions.microsoft.com> wrote in message
news:6cca01c401fd$90a802a0$a301280a@.phx.gbl...
> When I omit the restore log, I am unable to access the
> database. Enterprise Manager displays "(loading)" next to
> the database name.|||Try dropping the database before doing the restore.
I have found that doing filegroup restores using the REPLACE option creates
these type of errors.
Good Luck.
**********************************
"Paul Offerle" <pofferle@.fmcconnell.com> wrote in message
news:664a01c4016a$6821c020$a001280a@.phx.gbl...
> From time to time I receive the following error while
> restoring:
> "The log in this backup set terminates at LSNxxx, which
> is too early to apply to the database. A more recent log
> backup that includes LSNxxx can be restored."
> I am not backing up any logs. This is my backup command:
> BACKUP DATABASE [Order] TO DISK = N'C:\Program
> Files\Microsoft SQL Server\MSSQL\BACKUP\Orderback' WITH
> INIT , NOUNLOAD , NAME = N'Order backup', NOSKIP ,
> STATS = 10, NOFORMAT
> This is my restore:
> restore database [order]
> filegroup = 'primary', filegroup = 'ORDER1', filegroup
> = 'ORDER2'
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,norecovery,partial,replace,
> move 'order_data' to 'c:\program files\microsoft sql
> server\mssql\data\order_data.mdf',
> move 'order_data1' to 'c:\program files\microsoft sql
> server\mssql\data\order_data1.ndf',
> move 'order_data2' to 'c:\program files\microsoft sql
> server\mssql\data\order_data2.ndf',
> move 'order_log' to 'c:\program files\microsoft sql
> server\mssql\data\order_log.ldf'
> go
> restore log [order]
> from disk='c:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\Orderback'
> with file=1,recovery
> go|||ooops - I missed that the restore db didn't have recovery option..
Regards,
Greg Linwood
SQL Server MVP
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%238XCQEgAEHA.1420@.TK2MSFTNGP11.phx.gbl...
> Paul
> Although Greg said the restore database will "will fully restore the
> database and log entries in that file", he meant it COULD do the full
> restore, but only if you specify the keyword RECOVERY. The default is not
to
> run recovery, with the assumption that you will first be applying more
logs.
> Recovery needs to be run with the last thing you're restoring.
> Use the recovery option on your RESTORE DATABASE command and you won't
need
> to restore any logs.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> <anonymous@.discussions.microsoft.com> wrote in message
> news:6cca01c401fd$90a802a0$a301280a@.phx.gbl...
> > When I omit the restore log, I am unable to access the
> > database. Enterprise Manager displays "(loading)" next to
> > the database name.
>

Restore problem... "The media family on device '%ls' is incorrectly formed"

A client keeps sending me .BAK files. A couple have worked, but I
have gotten this error on many:
Error 3241 Severity 16 State 1
The media family on device '%ls' is incorrectly formed. SQL Server
cannot process this media family.
If I view the contents of the .BAK (in Enterprise Manager), it says it
is INCOMPLETE.
This indicates that maybe the backup was bad. However, since they have
sent me so many bad ones, my question is why are these backups turning
out bad?
Some details:
-The client is using SQL Server 2000 SP4, so am I
-I am running Win2K Server, they are running Win 2003 server.
-I looked at KB 297104 which deals with this error, but that is for
pre-SP4.
-When I run a restore verifyonly, I get the same error
Since I am off-site and can't go to the client site, any ideas on what
they may be doing wrong or what we can do for me to get a legitimate
copy of this database on my server? I am going crazy with these files
that won't load and don't know what to tell my client.have them run a verify before sending them to you. This should guarantee a
valid backup.
--
RelevantNoise.com - dedicated to mining blogs for business intelligence.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mike C" <michaeljc70@.hotmail.com> wrote in message
news:1187736521.741462.231380@.l22g2000prc.googlegroups.com...
>A client keeps sending me .BAK files. A couple have worked, but I
> have gotten this error on many:
> Error 3241 Severity 16 State 1
> The media family on device '%ls' is incorrectly formed. SQL Server
> cannot process this media family.
> If I view the contents of the .BAK (in Enterprise Manager), it says it
> is INCOMPLETE.
> This indicates that maybe the backup was bad. However, since they have
> sent me so many bad ones, my question is why are these backups turning
> out bad?
> Some details:
> -The client is using SQL Server 2000 SP4, so am I
> -I am running Win2K Server, they are running Win 2003 server.
> -I looked at KB 297104 which deals with this error, but that is for
> pre-SP4.
> -When I run a restore verifyonly, I get the same error
> Since I am off-site and can't go to the client site, any ideas on what
> they may be doing wrong or what we can do for me to get a legitimate
> copy of this database on my server? I am going crazy with these files
> that won't load and don't know what to tell my client.
>|||Hello,
First of all tell your client to do a restore with verify only or header only
to test, on their side, the correctness of the backup. If it's possible, tell
the client to do a full restore of the backup.
Second, if the first worked out well, send back the media to the client and
tell them to try the above process.
It is possible that between different copies of the backup file it becomes
corrupt. If the transfer of the backup file it is done over wan this is
something sure. A second possibility it is this file is part of a multivolume
backup. Sql Server has the option to backup a database to more than one file
to speed up the backup process.
Hope this helps you solve the problem.
I recommend you reading this too
http://www.dbforums.com/showthread.php?t=682406.
Cheers.
Mike C wrote:
>A client keeps sending me .BAK files. A couple have worked, but I
>have gotten this error on many:
>Error 3241 Severity 16 State 1
>The media family on device '%ls' is incorrectly formed. SQL Server
>cannot process this media family.
>If I view the contents of the .BAK (in Enterprise Manager), it says it
>is INCOMPLETE.
>This indicates that maybe the backup was bad. However, since they have
>sent me so many bad ones, my question is why are these backups turning
>out bad?
>Some details:
>-The client is using SQL Server 2000 SP4, so am I
>-I am running Win2K Server, they are running Win 2003 server.
>-I looked at KB 297104 which deals with this error, but that is for
>pre-SP4.
>-When I run a restore verifyonly, I get the same error
>Since I am off-site and can't go to the client site, any ideas on what
>they may be doing wrong or what we can do for me to get a legitimate
>copy of this database on my server? I am going crazy with these files
>that won't load and don't know what to tell my client.|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do arestorewith verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a fullrestoreof the backup.
> Second, if the first worked out well, send back themediato the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve theproblem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >Themediafamily on device '%ls' is incorrectly formed. SQL Server
> >cannot process thismediafamily.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run arestoreverifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
The client said they did a verify when they did the backup. I will
have them check to see if RESTORE VERIFYONLY works. Assuming the file
is good, I can only think of 2 unlikely issues:
-The file is becoming corrupt when they zip it up. Since it is bigger
than a DVD, that is the only way to get it to me.
-Running W2K Server vs. W2003 Server is making some dofference.|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do a restore with verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a full restore of the backup.
> Second, if the first worked out well, send back the media to the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve the problem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >The media family on device '%ls' is incorrectly formed. SQL Server
> >cannot process this media family.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run a restore verifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
The restore verifyonly or backuponly works at the client site. I
verified versions. They are using Sql Server 2000 SP3 (plus a
cumulative patch) while I am running SP4. I can try and go back to
SP3, but that seems unlikely culprit (more likely if their version
were higher than mine). Any other ideas?|||On Aug 22, 5:08 am, "flooriin" <u36842@.uwe> wrote:
> Hello,
> First of all tell your client to do a restore with verify only or header only
> to test, on their side, the correctness of the backup. If it's possible, tell
> the client to do a full restore of the backup.
> Second, if the first worked out well, send back the media to the client and
> tell them to try the above process.
> It is possible that between different copies of the backup file it becomes
> corrupt. If the transfer of the backup file it is done over wan this is
> something sure. A second possibility it is this file is part of a multivolume
> backup. Sql Server has the option to backup a database to more than one file
> to speed up the backup process.
> Hope this helps you solve the problem.
> I recommend you reading this toohttp://www.dbforums.com/showthread.php?t=682406.
> Cheers.
> Mike C wrote:
> >A client keeps sending me .BAK files. A couple have worked, but I
> >have gotten this error on many:
> >Error 3241 Severity 16 State 1
> >The media family on device '%ls' is incorrectly formed. SQL Server
> >cannot process this media family.
> >If I view the contents of the .BAK (in Enterprise Manager), it says it
> >is INCOMPLETE.
> >This indicates that maybe the backup was bad. However, since they have
> >sent me so many bad ones, my question is why are these backups turning
> >out bad?
> >Some details:
> >-The client is using SQL Server 2000 SP4, so am I
> >-I am running Win2K Server, they are running Win 2003 server.
> >-I looked at KB 297104 which deals with this error, but that is for
> >pre-SP4.
> >-When I run a restore verifyonly, I get the same error
> >Since I am off-site and can't go to the client site, any ideas on what
> >they may be doing wrong or what we can do for me to get a legitimate
> >copy of this database on my server? I am going crazy with these files
> >that won't load and don't know what to tell my client.
Do you think me being on w2K and them on W2003 server makes a
difference?|||I do not believe the problem arise because of different Windows versions. I
think it's more about database and the process to backup and deliver the
database. You have said that are cases when the backup was restored
successfully. What is different from your current situation? I am more
concern about different Sql Server version. I know about a bug in SP3 when a
differential database backup could miss to save some extents ... but you are
talking about full backup.
Read this too
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&messageid=167366&p=2
Maybe it will help you. Read the last post and try out the utility told
there.
Cheers.
Mike C wrote:
>> Hello,
>[quoted text clipped - 40 lines]
>> >copy of this database on my server? I am going crazy with these files
>> >that won't load and don't know what to tell my client.
>Do you think me being on w2K and them on W2003 server makes a
>difference?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200708/1|||On Aug 24, 6:25 am, "flooriin via SQLMonster.com" <u36842@.uwe> wrote:
> I do not believe the problem arise because of different Windows versions. I
> think it's more about database and the process to backup and deliver the
> database. You have said that are cases when the backup was restored
> successfully. What is different from your current situation? I am more
> concern about different Sql Server version. I know about a bug in SP3 when a
> differential database backup could miss to save some extents ... but you are
> talking about full backup.
> Read this toohttp://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=24&mes...
> Maybe it will help you. Read the last post and try out the utility told
> there.
> Cheers.
> Mike C wrote:
> >> Hello,
> >[quoted text clipped - 40 lines]
> >> >copy of this database on my server? I am going crazy with these files
> >> >that won't load and don't know what to tell my client.
> >Do you think me being on w2K and them on W2003 server makes a
> >difference?
> --
> Message posted via SQLMonster.comhttp://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200708/1
I installed SQL Server 2000 MSDE on an XP box and I was able to
restore the backup. That means the file is fine. I am just going to
work with that since I don't need any of the enterprise features.
This is a short project and it isn't worth spending 100 hrs trying to
figure out what the problem is.

Restore Problem - Error 5243

Dear All,

SQL : SQL Express 2005

I having a problem when trying to restore a database. there were around 10 databases, but one is giving the following error and restore fails, will be great if someone helps..

I also tried taking the backup to another site having SQL 2005 Standard edition, the same error comes.

--

TITLE: Microsoft SQL Server Management Studio

Restore failed for Server '.\SQL2K5'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

An inconsistency was detected during an internal operation. Please contact technical support. Reference number 8. (Microsoft SQL Server, Error: 5243)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=5243&LinkId=20476


BUTTONS:

OK

I also installed Service Pack, no luck..HELP!!!

HI,

Refer http://support.microsoft.com/kb/916086 which has workaround and hot fix for the problem.

Hemantgiri S. Goswami

|||

Hi,

Thanks for the reply. I went through that already and hence I applied the service pack 1. NO LUCK!!!

Good you pointed the KB link, I am just little confused.It says about "Creating and drop temporary tables...." and what I am doing is Restoring the DB from a backup..Does it mean while restoring temporary tables are created ?

Time is running out, HELP!!

No reply on this from Microsoft Support team!!! where are u guys?

Regards,

Restore Problem - Error 5243

Dear All,

SQL : SQL Express 2005

I having a problem when trying to restore a database. there were around 10 databases, but one is giving the following error and restore fails, will be great if someone helps..

I also tried taking the backup to another site having SQL 2005 Standard edition, the same error comes.

--

TITLE: Microsoft SQL Server Management Studio

Restore failed for Server '.\SQL2K5'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476


ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

An inconsistency was detected during an internal operation. Please contact technical support. Reference number 8. (Microsoft SQL Server, Error: 5243)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=5243&LinkId=20476


BUTTONS:

OK

I also installed Service Pack, no luck..HELP!!!

HI,

Refer http://support.microsoft.com/kb/916086 which has workaround and hot fix for the problem.

Hemantgiri S. Goswami

|||

Hi,

Thanks for the reply. I went through that already and hence I applied the service pack 1. NO LUCK!!!

Good you pointed the KB link, I am just little confused.It says about "Creating and drop temporary tables...." and what I am doing is Restoring the DB from a backup..Does it mean while restoring temporary tables are created ?

Time is running out, HELP!!

No reply on this from Microsoft Support team!!! where are u guys?

Regards,

Restore problem - anyone seen this error before?

I am having a problem restoring a database (SQL2000).
from a .bak file device. When I attempt a restore I get
the following message
"The media set for database xxx has 3 family members but
only 1 are provided. All memebers must be provided.
Restore database is terminating abnormally"
The .bak file has been zipped and unzipped with winzip9.
Could this have corrupted the file?
Regards
Neil Gibson
ngibson(revovethis)@.mclgroup.co.ukI think you may have made the database backup to multiple files. You need
to find the other 2 backup files to be able to restore the database.
Look in the msdb..backupmediafamily table on the server you made the backup
to find the names of the other 2 files if you don't know them.
<plug> If you need small backups, give MiniSQLBackup a spin. </plug>
Peter Yeoh
http://www.yohz.com
Need smaller backup files? Try MiniSQLBackup
"Neil Gibson" <anonymous@.discussions.microsoft.com> wrote in message
news:17b8a01c4494d$a81ed980$a001280a@.phx
.gbl...
> I am having a problem restoring a database (SQL2000).
> from a .bak file device. When I attempt a restore I get
> the following message
> "The media set for database xxx has 3 family members but
> only 1 are provided. All memebers must be provided.
> Restore database is terminating abnormally"
> The .bak file has been zipped and unzipped with winzip9.
> Could this have corrupted the file?
> Regards
> Neil Gibson
> ngibson(revovethis)@.mclgroup.co.uk

Restore problem - anyone seen this error before?

I am having a problem restoring a database (SQL2000).
from a .bak file device. When I attempt a restore I get
the following message
"The media set for database xxx has 3 family members but
only 1 are provided. All memebers must be provided.
Restore database is terminating abnormally"
The .bak file has been zipped and unzipped with winzip9.
Could this have corrupted the file?
Regards
Neil Gibson
ngibson(revovethis)@.mclgroup.co.uk
I think you may have made the database backup to multiple files. You need
to find the other 2 backup files to be able to restore the database.
Look in the msdb..backupmediafamily table on the server you made the backup
to find the names of the other 2 files if you don't know them.
<plug> If you need small backups, give MiniSQLBackup a spin. </plug>
Peter Yeoh
http://www.yohz.com
Need smaller backup files? Try MiniSQLBackup
"Neil Gibson" <anonymous@.discussions.microsoft.com> wrote in message
news:17b8a01c4494d$a81ed980$a001280a@.phx.gbl...
> I am having a problem restoring a database (SQL2000).
> from a .bak file device. When I attempt a restore I get
> the following message
> "The media set for database xxx has 3 family members but
> only 1 are provided. All memebers must be provided.
> Restore database is terminating abnormally"
> The .bak file has been zipped and unzipped with winzip9.
> Could this have corrupted the file?
> Regards
> Neil Gibson
> ngibson(revovethis)@.mclgroup.co.uk

Restore problem - anyone seen this error before?

I am having a problem restoring a database (SQL2000).
from a .bak file device. When I attempt a restore I get
the following message
"The media set for database xxx has 3 family members but
only 1 are provided. All memebers must be provided.
Restore database is terminating abnormally"
The .bak file has been zipped and unzipped with winzip9.
Could this have corrupted the file?
Regards
Neil Gibson
ngibson(revovethis)@.mclgroup.co.ukI think you may have made the database backup to multiple files. You need
to find the other 2 backup files to be able to restore the database.
Look in the msdb..backupmediafamily table on the server you made the backup
to find the names of the other 2 files if you don't know them.
<plug> If you need small backups, give MiniSQLBackup a spin. </plug>
Peter Yeoh
http://www.yohz.com
Need smaller backup files? Try MiniSQLBackup
"Neil Gibson" <anonymous@.discussions.microsoft.com> wrote in message
news:17b8a01c4494d$a81ed980$a001280a@.phx.gbl...
> I am having a problem restoring a database (SQL2000).
> from a .bak file device. When I attempt a restore I get
> the following message
> "The media set for database xxx has 3 family members but
> only 1 are provided. All memebers must be provided.
> Restore database is terminating abnormally"
> The .bak file has been zipped and unzipped with winzip9.
> Could this have corrupted the file?
> Regards
> Neil Gibson
> ngibson(revovethis)@.mclgroup.co.uk