Hi,
I have a problem during the recovery of the sql db dump.
A user had sql server installed in driver c, my application backed up a db
using 'backup database'. Later on the user reinstalled sql server to driver
d, and ran my application to do the recovery. The restore db was successful
but after restart my app it complained that cannot connect to the db. I foun
d
the db was restored in driver c but not in driver d.
How can I fix this problem?
Thanks
WilliamThe new installation of SQL server isn't aware of the restored database. Use
the sp_attach_ db stored procedure (or wizards in Enterprise Manager) to add
the database to the server.
"William" wrote:
> Hi,
> I have a problem during the recovery of the sql db dump.
> A user had sql server installed in driver c, my application backed up a db
> using 'backup database'. Later on the user reinstalled sql server to drive
r
> d, and ran my application to do the recovery. The restore db was successfu
l
> but after restart my app it complained that cannot connect to the db. I fo
und
> the db was restored in driver c but not in driver d.
> How can I fix this problem?
> Thanks
> Williamsql
Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
restore database using OSQL
Dear Sir/Madam,
Would you please help me to create a batch file to restore a database from a file located on a remote path to my MSDE installed on my workstation.
the original database location was on the D drive on the server
but when i want to restore it to my MSDE it will be in a different path which is C
I want to create a command batch file by just double clicking on it, it will restore the database. (i want a forced restoration).
Please proivde me with your help.
Regards,
HotBirdLook up RESTORE DATABASE in BOL. It's all there.|||Please check this script is it runnable and right
OSQL -U sa - P xxxx RESTORE DATABASE mydb FROM DISK = '\\195.xxx.xxx.xxx\dolphindata\30704'
WITH REPLACE, MOVE 'mydb_Data' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_Data.MDF',MOVE 'mydb_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_LOG.LDF' QUIT
I put this script in a file called "restore.bat"
Please advise me
Thanks in advance
HotBird|||Surround your RESTORE...by quotation marks and loose QUIT:
OSQL -U sa - P xxxx "RESTORE DATABASE mydb FROM DISK = '\\195.xxx.xxx.xxx\dolphindata\30704'
WITH REPLACE, MOVE 'mydb_Data' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_Data.MDF',MOVE 'mydb_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_LOG.LDF'"
Would you please help me to create a batch file to restore a database from a file located on a remote path to my MSDE installed on my workstation.
the original database location was on the D drive on the server
but when i want to restore it to my MSDE it will be in a different path which is C
I want to create a command batch file by just double clicking on it, it will restore the database. (i want a forced restoration).
Please proivde me with your help.
Regards,
HotBirdLook up RESTORE DATABASE in BOL. It's all there.|||Please check this script is it runnable and right
OSQL -U sa - P xxxx RESTORE DATABASE mydb FROM DISK = '\\195.xxx.xxx.xxx\dolphindata\30704'
WITH REPLACE, MOVE 'mydb_Data' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_Data.MDF',MOVE 'mydb_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_LOG.LDF' QUIT
I put this script in a file called "restore.bat"
Please advise me
Thanks in advance
HotBird|||Surround your RESTORE...by quotation marks and loose QUIT:
OSQL -U sa - P xxxx "RESTORE DATABASE mydb FROM DISK = '\\195.xxx.xxx.xxx\dolphindata\30704'
WITH REPLACE, MOVE 'mydb_Data' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_Data.MDF',MOVE 'mydb_Log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL\Data\mydb_LOG.LDF'"
restore database to different partition
Our client has an SBS 2000 server with SQL 2000 installed.
The server has 3 separate physical hard drives. I am
moving the data to a new server with 1 large physical hard
drive. My question is what is the easiest method to move
the data from the old server to the new server, keeping in
mind that the partions are changing. I don't want to
create the partions on the new server.
Thanks for the help,
JohnSee sp_attach_db and sp_detach_db in BOL. Or you can use
DTS or the backup/ restore method.
>--Original Message--
>Our client has an SBS 2000 server with SQL 2000
installed.
>The server has 3 separate physical hard drives. I am
>moving the data to a new server with 1 large physical
hard
>drive. My question is what is the easiest method to move
>the data from the old server to the new server, keeping
in
>mind that the partions are changing. I don't want to
>create the partions on the new server.
>Thanks for the help,
>John
>.
>|||I like the Copy Wizard myself.
Put database in single user mode.
Right click on server in ent. mgr, then do all tasks/Copy
Database Wizard.
>--Original Message--
>Our client has an SBS 2000 server with SQL 2000
installed.
>The server has 3 separate physical hard drives. I am
>moving the data to a new server with 1 large physical
hard
>drive. My question is what is the easiest method to move
>the data from the old server to the new server, keeping
in
>mind that the partions are changing. I don't want to
>create the partions on the new server.
>Thanks for the help,
>John
>.
>|||Here are some good articles:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"John Chase" <johnc@.hcd.net> wrote in message news:06a001c39efe$b1f08e80$a001280a@.phx.gbl...
> Our client has an SBS 2000 server with SQL 2000 installed.
> The server has 3 separate physical hard drives. I am
> moving the data to a new server with 1 large physical hard
> drive. My question is what is the easiest method to move
> the data from the old server to the new server, keeping in
> mind that the partions are changing. I don't want to
> create the partions on the new server.
> Thanks for the help,
> John
The server has 3 separate physical hard drives. I am
moving the data to a new server with 1 large physical hard
drive. My question is what is the easiest method to move
the data from the old server to the new server, keeping in
mind that the partions are changing. I don't want to
create the partions on the new server.
Thanks for the help,
JohnSee sp_attach_db and sp_detach_db in BOL. Or you can use
DTS or the backup/ restore method.
>--Original Message--
>Our client has an SBS 2000 server with SQL 2000
installed.
>The server has 3 separate physical hard drives. I am
>moving the data to a new server with 1 large physical
hard
>drive. My question is what is the easiest method to move
>the data from the old server to the new server, keeping
in
>mind that the partions are changing. I don't want to
>create the partions on the new server.
>Thanks for the help,
>John
>.
>|||I like the Copy Wizard myself.
Put database in single user mode.
Right click on server in ent. mgr, then do all tasks/Copy
Database Wizard.
>--Original Message--
>Our client has an SBS 2000 server with SQL 2000
installed.
>The server has 3 separate physical hard drives. I am
>moving the data to a new server with 1 large physical
hard
>drive. My question is what is the easiest method to move
>the data from the old server to the new server, keeping
in
>mind that the partions are changing. I don't want to
>create the partions on the new server.
>Thanks for the help,
>John
>.
>|||Here are some good articles:
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"John Chase" <johnc@.hcd.net> wrote in message news:06a001c39efe$b1f08e80$a001280a@.phx.gbl...
> Our client has an SBS 2000 server with SQL 2000 installed.
> The server has 3 separate physical hard drives. I am
> moving the data to a new server with 1 large physical hard
> drive. My question is what is the easiest method to move
> the data from the old server to the new server, keeping in
> mind that the partions are changing. I don't want to
> create the partions on the new server.
> Thanks for the help,
> John
Restore database stuck on (Loading)
I recently installed MSDE on a laptop. I then restored several databases from backup files without problem. However, one database is constantly stuck at the grey colour displaying the (Loading) message.
Why won't this database restore ? It is of course the most important database and I only have the one backup file.
This only appears to fail on his server. Do I need to uninstall MSDE and start over ?It's probably the machine's "critical need detector", it might be a wee bit too sensitive or mis-adjusted.
On a slightly more serious note, what tools are you using to do the restore? The only tool that could do a restore that ships with MSDE is OSQL.EXE, and I'm pretty comfortable that you aren't using that! Enterprise Mangler would be my first guess, but that is still only a guess.
Could the dump (backup) have been made with a later service pack than you are using to restore it? That can make things get really crabby sometimes.
Is the database file one that this instance of MSDE can handle? Depending on the MSDE version, you can handle up to 2 Gb of data (although I've seen data and log dumps over 10 Gb).
If none of those ideas pan out, then my first suggestion would be to:
1 Disable everything you can that uses MSDE (keep notes!)
2 Stop the MSDE service
3 Restart the MSDE service
4 Try to load the offending database
5 If you can't load the database, stop the MSDE service
6 Examine the Errorlog file carefully
7 If you can't find anything in the Errorlog, consider posting it here.
8 if the database can be posted, consider posting the backup too for us to play with!
-PatP|||If it's in Loading state, could it be that you are restoring from a backup device that contained incomplete set of full db backup and some trx logs?|||But it restores without fail on any number of other servers. So I think the backup file is ok.
I have gone through the steps above and can't see anything wrong. I have pasted the errorlog below for perusal.
Yes I am using Enterprise manager. I also tried the restore database command from isqlw utility and that also produced the error :
Processed 8432 pages for database 'IPSHOW_NEW', file 'IPSHOW_Data' on file 1.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Processed 1 pages for database 'IPSHOW_NEW', file 'IPSHOW_Log' on file 1.
Connection Broken
Errorlog
2004-12-23 15:56:36.01 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2004-12-23 15:56:36.01 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-12-23 15:56:36.01 server All rights reserved.
2004-12-23 15:56:36.01 server Server Process ID is 1392.
2004-12-23 15:56:36.01 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2004-12-23 15:56:36.09 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-12-23 15:56:36.13 server SQL Server configured for thread mode processing.
2004-12-23 15:56:36.13 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-12-23 15:56:36.15 spid3 Starting up database 'master'.
2004-12-23 15:56:36.53 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-12-23 15:56:36.53 spid5 Starting up database 'model'.
2004-12-23 15:56:36.68 spid3 Server name is 'SBUTLER'.
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 4
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 5
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 6
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 9
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 10
2004-12-23 15:56:36.68 spid3 Starting up database 'IPSHOW_NEW'.
2004-12-23 15:56:36.68 server SQL server listening on 192.168.1.110: 1433.
2004-12-23 15:56:36.69 server SQL server listening on 127.0.0.1: 1433.
2004-12-23 15:56:36.98 spid3 Bypassing recovery for database 'IPSHOW_NEW' because it is marked IN LOAD.
2004-12-23 15:56:37.09 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-12-23 15:56:37.09 server SQL Server is ready for client connections
2004-12-23 15:56:37.22 spid5 Clearing tempdb database.
2004-12-23 15:56:38.58 spid5 Starting up database 'tempdb'.
2004-12-23 15:56:38.78 spid3 Recovery complete.
2004-12-23 15:56:38.78 spid3 SQL global counter collection task is created.
2004-12-23 15:57:35.63 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
2004-12-23 15:57:35.78 spid51 Starting up database 'msdb'.|||Post the statement used in ISQL to restore the database.
And ensure the backup file is stored on the MSDE server and if you are trying to restore from a network location due to th network issues it may be failing with the above error.
Refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;827452 for relevancy.|||I gave up and uninstalled MSDE. As it turns out he required Reporting Services and a Developer Edition of SQL Server so all for the best in the end. Thanks for the assistance.
Why won't this database restore ? It is of course the most important database and I only have the one backup file.
This only appears to fail on his server. Do I need to uninstall MSDE and start over ?It's probably the machine's "critical need detector", it might be a wee bit too sensitive or mis-adjusted.
On a slightly more serious note, what tools are you using to do the restore? The only tool that could do a restore that ships with MSDE is OSQL.EXE, and I'm pretty comfortable that you aren't using that! Enterprise Mangler would be my first guess, but that is still only a guess.
Could the dump (backup) have been made with a later service pack than you are using to restore it? That can make things get really crabby sometimes.
Is the database file one that this instance of MSDE can handle? Depending on the MSDE version, you can handle up to 2 Gb of data (although I've seen data and log dumps over 10 Gb).
If none of those ideas pan out, then my first suggestion would be to:
1 Disable everything you can that uses MSDE (keep notes!)
2 Stop the MSDE service
3 Restart the MSDE service
4 Try to load the offending database
5 If you can't load the database, stop the MSDE service
6 Examine the Errorlog file carefully
7 If you can't find anything in the Errorlog, consider posting it here.
8 if the database can be posted, consider posting the backup too for us to play with!
-PatP|||If it's in Loading state, could it be that you are restoring from a backup device that contained incomplete set of full db backup and some trx logs?|||But it restores without fail on any number of other servers. So I think the backup file is ok.
I have gone through the steps above and can't see anything wrong. I have pasted the errorlog below for perusal.
Yes I am using Enterprise manager. I also tried the restore database command from isqlw utility and that also produced the error :
Processed 8432 pages for database 'IPSHOW_NEW', file 'IPSHOW_Data' on file 1.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Processed 1 pages for database 'IPSHOW_NEW', file 'IPSHOW_Log' on file 1.
Connection Broken
Errorlog
2004-12-23 15:56:36.01 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2004-12-23 15:56:36.01 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-12-23 15:56:36.01 server All rights reserved.
2004-12-23 15:56:36.01 server Server Process ID is 1392.
2004-12-23 15:56:36.01 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2004-12-23 15:56:36.09 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-12-23 15:56:36.13 server SQL Server configured for thread mode processing.
2004-12-23 15:56:36.13 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-12-23 15:56:36.15 spid3 Starting up database 'master'.
2004-12-23 15:56:36.53 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-12-23 15:56:36.53 spid5 Starting up database 'model'.
2004-12-23 15:56:36.68 spid3 Server name is 'SBUTLER'.
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 4
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 5
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 6
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 9
2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 10
2004-12-23 15:56:36.68 spid3 Starting up database 'IPSHOW_NEW'.
2004-12-23 15:56:36.68 server SQL server listening on 192.168.1.110: 1433.
2004-12-23 15:56:36.69 server SQL server listening on 127.0.0.1: 1433.
2004-12-23 15:56:36.98 spid3 Bypassing recovery for database 'IPSHOW_NEW' because it is marked IN LOAD.
2004-12-23 15:56:37.09 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-12-23 15:56:37.09 server SQL Server is ready for client connections
2004-12-23 15:56:37.22 spid5 Clearing tempdb database.
2004-12-23 15:56:38.58 spid5 Starting up database 'tempdb'.
2004-12-23 15:56:38.78 spid3 Recovery complete.
2004-12-23 15:56:38.78 spid3 SQL global counter collection task is created.
2004-12-23 15:57:35.63 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
2004-12-23 15:57:35.78 spid51 Starting up database 'msdb'.|||Post the statement used in ISQL to restore the database.
And ensure the backup file is stored on the MSDE server and if you are trying to restore from a network location due to th network issues it may be failing with the above error.
Refer to this KBA http://support.microsoft.com/default.aspx?scid=kb;en-us;827452 for relevancy.|||I gave up and uninstalled MSDE. As it turns out he required Reporting Services and a Developer Edition of SQL Server so all for the best in the end. Thanks for the assistance.
Friday, March 23, 2012
Restore database from Yukon June CTP to September CTP
Hello:
I am trying to restore a database that was created with the June CTP version of Yukon to another box that has the September CTP installed. However, I am getting the following error:
-
"The database was backed up on a server running version 9.00.0852. That version is incompatible with this server, which is running version 9.00.1314. Either restore the database on a server that supports the backup or use a backup that is compatible with this server.
RESTORE DATABASE is terminating abnormally, (Microsoft SQL Server, Error: 3169)"
-
Shouldn't the September CTP be backward compatible with the June CTP? Would appreciate it if someone has any ideas on how to resolve this. I have verified the compatibility level to be 90 on the September CTP.
Thanks!
If you haven't uninstalled June yet, this might work. A kludge to be sure, and not for large databases.
Solution? Import the database to access. Save the create scripts to a file.
Then recreate the schema in Sept and use the Access Upsize Wizard to load the data.
Not ideal. However, it should work.
sqlRestore Database from file
Hello, I had backed up a database from SQL 2000, just before I format my computer. Now I have installed SQL 2005 and trying to restore that database to it, it doesn't work and I get the following error when doing that
===================================
Restore failed for Server 'localhost\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
Program Location:
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()
===================================
System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing '2for1' database. (Microsoft.SqlServer.Express.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&LinkId=20476
Program Location:
at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection queries, ServerMessageEventHandler dbccMessageHandler, Boolean errorsAsMessages)
at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server server, StringCollection queries)
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
========================================================
any help is appreciated
Thanks,
COuld you please post the command you were issueing in your program ?-Jens Suessmeyer.|||
Thank you for your kind reply.
I didn't use command to restore the database from file but I did it through SQL Server Management Studio Express CTP
|||I've also tried the following command to restore from file
RESTORE DATABASE [2for1] FROM DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\db' WITH FILE = 1, NOUNLOAD, STATS = 10
GO
|||Hi,
I guess your are not the same as from the server your backup was originally taken from, right ? Then you have to use the WITH MOVE option. (From BOL)
[ [ , ] MOVE 'logical_file_name' TO 'operating_system_file_name' ]
This will help you to place them on a destination that exists on your system.
HTH, jens Suessmeyer.
Wednesday, March 21, 2012
restore database back to sql 7.0?
Hi,
I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
(win2k) is installed. I was transferring one of the database (db1) from 7.0
to 2000 by using copy database wizard. But I found that instead of copying,
it actually moved the db1 to the new server. Since the new server is not in
production stage, I want to restore the db1 back to 7.0. I can see the data
and log files are still there. How can I have it operational again?
Please help me with this, I would greatly appreciate it.
Thanks a lot,
SarahAre the original data and log files still on the 7.0 server? If so, you can
reattach the original files to 7.0 using sp_attach_db. Otherwise, you'll
need to restore the 7.0 database from a 7.0 backup.
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
As I understand it a restore from version 2000 to 7 is not possible and
would require the database/objects/data to be recreated via scripts, DTS
and/or BCP.
Was there a script location that contains the schema and data files for the
upgrade? Might be able to leverage from that.
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
Optionally if you have a backup of the v7 database you could just restore
it - would be alot easier if the backup exists!
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Thanks Lori and Jerry for your quick response. Both of you have a same
solution which is to use backup. We are using veritas backup exec to backup
SQL7.0. I've been trying to restore the database to the server. For some
reason, all failed.
Yes, all of the data and log files are still on SQL 7.0 under
\mssql\data\db1_data.mdf and db1_log.ldf.
I will try Lori, reattach the db1 to see first, if it is not working, I will
come back to you.
Thanks a lot,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Hi Lori,
I tried, query:
sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
'd:\mssql7\data\db1_log.ldf'
But I got the error message saying, "I/O error (bad page id)......
connection broken.
What does this mean? Is the file corrupt?
Thanks,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
> Thanks Lori and Jerry for your quick response. Both of you have a same
> solution which is to use backup. We are using veritas backup exec to
> backup SQL7.0. I've been trying to restore the database to the server. For
> some reason, all failed.
> Yes, all of the data and log files are still on SQL 7.0 under
> \mssql\data\db1_data.mdf and db1_log.ldf.
> I will try Lori, reattach the db1 to see first, if it is not working, I
> will come back to you.
> Thanks a lot,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to 7.0.
>> I can see the data and log files are still there. How can I have it
>> operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>|||Not sure, but usually I/O errors indicate database corruption or hardware
issues. Did you do a dbcc checkdb before you did the copy/move? Are you
sure that the files you're trying to attach are SQL 7.0 files?
"SG" <sguo@.coopervision.ca> wrote in message
news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
> 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I
>> will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to
>> 7.0. I can see the data and log files are still there. How can I have it
>> operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>|||attach is only guaranteed if you actually detached the database first. Are you saying that you don't
have a database backup of the 7.0 database? That you only "ripped" the database files using Veritas?
You could try creating a database on the 7.0 server with same db name and same file names, stop the
SQL Server, delete the new files and copy your old files in place of the new ones.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same solution which is to use
>> backup. We are using veritas backup exec to backup SQL7.0. I've been trying to restore the
>> database to the server. For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under \mssql\data\db1_data.mdf and
>> db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000 (win2k) is installed. I
>> was transferring one of the database (db1) from 7.0 to 2000 by using copy database wizard. But I
>> found that instead of copying, it actually moved the db1 to the new server. Since the new server
>> is not in production stage, I want to restore the db1 back to 7.0. I can see the data and log
>> files are still there. How can I have it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>|||Hi Lori,
Yes, I'm sure that file is SQL7.0. But I forgot one thing, while I was doing
"Copy database" from 7.0 to 2k, there was an error "detach failed". I guess
that is where the problem was. Instead of copying, it did move. Before done
this database, I did a small database test, it was fine. Don't know what
happened.
Any idea?
Thanks,
Sarah
"Lori Clark" <lclark@.dbadvisor.com> wrote in message
news:uSfds42zFHA.904@.tk2msftngp13.phx.gbl...
> Not sure, but usually I/O errors indicate database corruption or hardware
> issues. Did you do a dbcc checkdb before you did the copy/move? Are you
> sure that the files you're trying to attach are SQL 7.0 files?
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
>> 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I
>> will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to
>> 7.0. I can see the data and log files are still there. How can I have
>> it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>|||Hi Tibor,
I did get an error while I was copy the database about "Detach database
failed".
We have Veritas backup agent for SQL on SQL 7.0 server, it should actually
backup the database not only "ripped" the files. I might need to try your
suggestion in this case. If I create the new database, I like to use the
data file, but not the log file. Can I use new log file with the old data
file?
It turned really mess now. Does anybody have any note before I do the "copy
database wizard"? I do have another very important database needs to be
transferred from 7.0 to 2k. I cannot afford to have the same mistake.
Appreciate your idea,
Sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
> attach is only guaranteed if you actually detached the database first. Are
> you saying that you don't have a database backup of the 7.0 database? That
> you only "ripped" the database files using Veritas? You could try creating
> a database on the 7.0 server with same db name and same file names, stop
> the SQL Server, delete the new files and copy your old files in place of
> the new ones.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
>> 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I
>> will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to
>> 7.0. I can see the data and log files are still there. How can I have
>> it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>|||> We have Veritas backup agent for SQL on SQL 7.0 server, it should actually backup the database
If so, you are most probably fine. You would have a SQL Server backup of the database, and you can
use the TSQL RESTORE command to restore it.
> If I create the new database, I like to use the data file, but not the log file. Can I use new log
> file with the old data file?
Most probably not. Read in Books Online about what the recovery process does and you will
understand. You could try without the log file and see if SQL Server can create a log file for you.
But if the attach failed, probably this will as well.
But first you need to determine whether you have a copy of the database file or a backup of the
database...
> Does anybody have any note before I do the "copy database wizard"?
Don't. Use sp_detach_db and sp_attach_db instead. Then you can use DTS for the other tasks that the
CDW has. This gives you control.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:O84LYx$zFHA.3856@.tk2msftngp13.phx.gbl...
> Hi Tibor,
> I did get an error while I was copy the database about "Detach database failed".
> We have Veritas backup agent for SQL on SQL 7.0 server, it should actually backup the database not
> only "ripped" the files. I might need to try your suggestion in this case. If I create the new
> database, I like to use the data file, but not the log file. Can I use new log file with the old
> data file?
> It turned really mess now. Does anybody have any note before I do the "copy database wizard"? I do
> have another very important database needs to be transferred from 7.0 to 2k. I cannot afford to
> have the same mistake.
> Appreciate your idea,
> Sarah
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
>> attach is only guaranteed if you actually detached the database first. Are you saying that you
>> don't have a database backup of the 7.0 database? That you only "ripped" the database files using
>> Veritas? You could try creating a database on the 7.0 server with same db name and same file
>> names, stop the SQL Server, delete the new files and copy your old files in place of the new
>> ones.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same solution which is to use
>> backup. We are using veritas backup exec to backup SQL7.0. I've been trying to restore the
>> database to the server. For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under \mssql\data\db1_data.mdf and
>> db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000 (win2k) is installed. I
>> was transferring one of the database (db1) from 7.0 to 2000 by using copy database wizard. But
>> I found that instead of copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to 7.0. I can see the data
>> and log files are still there. How can I have it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>>
>|||Hi Tibor,
Thanks so much for your comments. I will check the backup again. That's the
best way.
Thanks,
sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OH39WPA0FHA.720@.TK2MSFTNGP15.phx.gbl...
>> We have Veritas backup agent for SQL on SQL 7.0 server, it should
>> actually backup the database
> If so, you are most probably fine. You would have a SQL Server backup of
> the database, and you can use the TSQL RESTORE command to restore it.
>
>> If I create the new database, I like to use the data file, but not the
>> log file. Can I use new log file with the old data file?
> Most probably not. Read in Books Online about what the recovery process
> does and you will understand. You could try without the log file and see
> if SQL Server can create a log file for you. But if the attach failed,
> probably this will as well.
> But first you need to determine whether you have a copy of the database
> file or a backup of the database...
>
>> Does anybody have any note before I do the "copy database wizard"?
> Don't. Use sp_detach_db and sp_attach_db instead. Then you can use DTS for
> the other tasks that the CDW has. This gives you control.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:O84LYx$zFHA.3856@.tk2msftngp13.phx.gbl...
>> Hi Tibor,
>> I did get an error while I was copy the database about "Detach database
>> failed".
>> We have Veritas backup agent for SQL on SQL 7.0 server, it should
>> actually backup the database not only "ripped" the files. I might need to
>> try your suggestion in this case. If I create the new database, I like to
>> use the data file, but not the log file. Can I use new log file with the
>> old data file?
>> It turned really mess now. Does anybody have any note before I do the
>> "copy database wizard"? I do have another very important database needs
>> to be transferred from 7.0 to 2k. I cannot afford to have the same
>> mistake.
>> Appreciate your idea,
>> Sarah
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
>> attach is only guaranteed if you actually detached the database first.
>> Are you saying that you don't have a database backup of the 7.0
>> database? That you only "ripped" the database files using Veritas? You
>> could try creating a database on the 7.0 server with same db name and
>> same file names, stop the SQL Server, delete the new files and copy your
>> old files in place of the new ones.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
>> 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working,
>> I will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1)
>> from 7.0 to 2000 by using copy database wizard. But I found that
>> instead of copying, it actually moved the db1 to the new server.
>> Since the new server is not in production stage, I want to restore
>> the db1 back to 7.0. I can see the data and log files are still
>> there. How can I have it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>>
>>
>
I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
(win2k) is installed. I was transferring one of the database (db1) from 7.0
to 2000 by using copy database wizard. But I found that instead of copying,
it actually moved the db1 to the new server. Since the new server is not in
production stage, I want to restore the db1 back to 7.0. I can see the data
and log files are still there. How can I have it operational again?
Please help me with this, I would greatly appreciate it.
Thanks a lot,
SarahAre the original data and log files still on the 7.0 server? If so, you can
reattach the original files to 7.0 using sp_attach_db. Otherwise, you'll
need to restore the 7.0 database from a 7.0 backup.
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
As I understand it a restore from version 2000 to 7 is not possible and
would require the database/objects/data to be recreated via scripts, DTS
and/or BCP.
Was there a script location that contains the schema and data files for the
upgrade? Might be able to leverage from that.
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
Optionally if you have a backup of the v7 database you could just restore
it - would be alot easier if the backup exists!
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Thanks Lori and Jerry for your quick response. Both of you have a same
solution which is to use backup. We are using veritas backup exec to backup
SQL7.0. I've been trying to restore the database to the server. For some
reason, all failed.
Yes, all of the data and log files are still on SQL 7.0 under
\mssql\data\db1_data.mdf and db1_log.ldf.
I will try Lori, reattach the db1 to see first, if it is not working, I will
come back to you.
Thanks a lot,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Hi Lori,
I tried, query:
sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
'd:\mssql7\data\db1_log.ldf'
But I got the error message saying, "I/O error (bad page id)......
connection broken.
What does this mean? Is the file corrupt?
Thanks,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
> Thanks Lori and Jerry for your quick response. Both of you have a same
> solution which is to use backup. We are using veritas backup exec to
> backup SQL7.0. I've been trying to restore the database to the server. For
> some reason, all failed.
> Yes, all of the data and log files are still on SQL 7.0 under
> \mssql\data\db1_data.mdf and db1_log.ldf.
> I will try Lori, reattach the db1 to see first, if it is not working, I
> will come back to you.
> Thanks a lot,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to 7.0.
>> I can see the data and log files are still there. How can I have it
>> operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>|||Not sure, but usually I/O errors indicate database corruption or hardware
issues. Did you do a dbcc checkdb before you did the copy/move? Are you
sure that the files you're trying to attach are SQL 7.0 files?
"SG" <sguo@.coopervision.ca> wrote in message
news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
> 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I
>> will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to
>> 7.0. I can see the data and log files are still there. How can I have it
>> operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>|||attach is only guaranteed if you actually detached the database first. Are you saying that you don't
have a database backup of the 7.0 database? That you only "ripped" the database files using Veritas?
You could try creating a database on the 7.0 server with same db name and same file names, stop the
SQL Server, delete the new files and copy your old files in place of the new ones.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same solution which is to use
>> backup. We are using veritas backup exec to backup SQL7.0. I've been trying to restore the
>> database to the server. For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under \mssql\data\db1_data.mdf and
>> db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000 (win2k) is installed. I
>> was transferring one of the database (db1) from 7.0 to 2000 by using copy database wizard. But I
>> found that instead of copying, it actually moved the db1 to the new server. Since the new server
>> is not in production stage, I want to restore the db1 back to 7.0. I can see the data and log
>> files are still there. How can I have it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>|||Hi Lori,
Yes, I'm sure that file is SQL7.0. But I forgot one thing, while I was doing
"Copy database" from 7.0 to 2k, there was an error "detach failed". I guess
that is where the problem was. Instead of copying, it did move. Before done
this database, I did a small database test, it was fine. Don't know what
happened.
Any idea?
Thanks,
Sarah
"Lori Clark" <lclark@.dbadvisor.com> wrote in message
news:uSfds42zFHA.904@.tk2msftngp13.phx.gbl...
> Not sure, but usually I/O errors indicate database corruption or hardware
> issues. Did you do a dbcc checkdb before you did the copy/move? Are you
> sure that the files you're trying to attach are SQL 7.0 files?
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
>> 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I
>> will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to
>> 7.0. I can see the data and log files are still there. How can I have
>> it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>|||Hi Tibor,
I did get an error while I was copy the database about "Detach database
failed".
We have Veritas backup agent for SQL on SQL 7.0 server, it should actually
backup the database not only "ripped" the files. I might need to try your
suggestion in this case. If I create the new database, I like to use the
data file, but not the log file. Can I use new log file with the old data
file?
It turned really mess now. Does anybody have any note before I do the "copy
database wizard"? I do have another very important database needs to be
transferred from 7.0 to 2k. I cannot afford to have the same mistake.
Appreciate your idea,
Sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
> attach is only guaranteed if you actually detached the database first. Are
> you saying that you don't have a database backup of the 7.0 database? That
> you only "ripped" the database files using Veritas? You could try creating
> a database on the 7.0 server with same db name and same file names, stop
> the SQL Server, delete the new files and copy your old files in place of
> the new ones.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
>> 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I
>> will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1) from
>> 7.0 to 2000 by using copy database wizard. But I found that instead of
>> copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to
>> 7.0. I can see the data and log files are still there. How can I have
>> it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>|||> We have Veritas backup agent for SQL on SQL 7.0 server, it should actually backup the database
If so, you are most probably fine. You would have a SQL Server backup of the database, and you can
use the TSQL RESTORE command to restore it.
> If I create the new database, I like to use the data file, but not the log file. Can I use new log
> file with the old data file?
Most probably not. Read in Books Online about what the recovery process does and you will
understand. You could try without the log file and see if SQL Server can create a log file for you.
But if the attach failed, probably this will as well.
But first you need to determine whether you have a copy of the database file or a backup of the
database...
> Does anybody have any note before I do the "copy database wizard"?
Don't. Use sp_detach_db and sp_attach_db instead. Then you can use DTS for the other tasks that the
CDW has. This gives you control.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:O84LYx$zFHA.3856@.tk2msftngp13.phx.gbl...
> Hi Tibor,
> I did get an error while I was copy the database about "Detach database failed".
> We have Veritas backup agent for SQL on SQL 7.0 server, it should actually backup the database not
> only "ripped" the files. I might need to try your suggestion in this case. If I create the new
> database, I like to use the data file, but not the log file. Can I use new log file with the old
> data file?
> It turned really mess now. Does anybody have any note before I do the "copy database wizard"? I do
> have another very important database needs to be transferred from 7.0 to 2k. I cannot afford to
> have the same mistake.
> Appreciate your idea,
> Sarah
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
>> attach is only guaranteed if you actually detached the database first. Are you saying that you
>> don't have a database backup of the 7.0 database? That you only "ripped" the database files using
>> Veritas? You could try creating a database on the 7.0 server with same db name and same file
>> names, stop the SQL Server, delete the new files and copy your old files in place of the new
>> ones.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same solution which is to use
>> backup. We are using veritas backup exec to backup SQL7.0. I've been trying to restore the
>> database to the server. For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under \mssql\data\db1_data.mdf and
>> db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working, I will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000 (win2k) is installed. I
>> was transferring one of the database (db1) from 7.0 to 2000 by using copy database wizard. But
>> I found that instead of copying, it actually moved the db1 to the new server. Since the new
>> server is not in production stage, I want to restore the db1 back to 7.0. I can see the data
>> and log files are still there. How can I have it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>>
>|||Hi Tibor,
Thanks so much for your comments. I will check the backup again. That's the
best way.
Thanks,
sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OH39WPA0FHA.720@.TK2MSFTNGP15.phx.gbl...
>> We have Veritas backup agent for SQL on SQL 7.0 server, it should
>> actually backup the database
> If so, you are most probably fine. You would have a SQL Server backup of
> the database, and you can use the TSQL RESTORE command to restore it.
>
>> If I create the new database, I like to use the data file, but not the
>> log file. Can I use new log file with the old data file?
> Most probably not. Read in Books Online about what the recovery process
> does and you will understand. You could try without the log file and see
> if SQL Server can create a log file for you. But if the attach failed,
> probably this will as well.
> But first you need to determine whether you have a copy of the database
> file or a backup of the database...
>
>> Does anybody have any note before I do the "copy database wizard"?
> Don't. Use sp_detach_db and sp_attach_db instead. Then you can use DTS for
> the other tasks that the CDW has. This gives you control.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:O84LYx$zFHA.3856@.tk2msftngp13.phx.gbl...
>> Hi Tibor,
>> I did get an error while I was copy the database about "Detach database
>> failed".
>> We have Veritas backup agent for SQL on SQL 7.0 server, it should
>> actually backup the database not only "ripped" the files. I might need to
>> try your suggestion in this case. If I create the new database, I like to
>> use the data file, but not the log file. Can I use new log file with the
>> old data file?
>> It turned really mess now. Does anybody have any note before I do the
>> "copy database wizard"? I do have another very important database needs
>> to be transferred from 7.0 to 2k. I cannot afford to have the same
>> mistake.
>> Appreciate your idea,
>> Sarah
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
>> attach is only guaranteed if you actually detached the database first.
>> Are you saying that you don't have a database backup of the 7.0
>> database? That you only "ripped" the database files using Veritas? You
>> could try creating a database on the 7.0 server with same db name and
>> same file names, stop the SQL Server, delete the new files and copy your
>> old files in place of the new ones.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>> Hi Lori,
>> I tried, query:
>> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
>> 'd:\mssql7\data\db1_log.ldf'
>> But I got the error message saying, "I/O error (bad page id)......
>> connection broken.
>> What does this mean? Is the file corrupt?
>> Thanks,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>> Thanks Lori and Jerry for your quick response. Both of you have a same
>> solution which is to use backup. We are using veritas backup exec to
>> backup SQL7.0. I've been trying to restore the database to the server.
>> For some reason, all failed.
>> Yes, all of the data and log files are still on SQL 7.0 under
>> \mssql\data\db1_data.mdf and db1_log.ldf.
>> I will try Lori, reattach the db1 to see first, if it is not working,
>> I will come back to you.
>> Thanks a lot,
>> Sarah
>> "SG" <sguo@.coopervision.ca> wrote in message
>> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
>> (win2k) is installed. I was transferring one of the database (db1)
>> from 7.0 to 2000 by using copy database wizard. But I found that
>> instead of copying, it actually moved the db1 to the new server.
>> Since the new server is not in production stage, I want to restore
>> the db1 back to 7.0. I can see the data and log files are still
>> there. How can I have it operational again?
>> Please help me with this, I would greatly appreciate it.
>> Thanks a lot,
>> Sarah
>>
>>
>>
>>
>
restore database back to sql 7.0?
Hi,
I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
(win2k) is installed. I was transferring one of the database (db1) from 7.0
to 2000 by using copy database wizard. But I found that instead of copying,
it actually moved the db1 to the new server. Since the new server is not in
production stage, I want to restore the db1 back to 7.0. I can see the data
and log files are still there. How can I have it operational again?
Please help me with this, I would greatly appreciate it.
Thanks a lot,
SarahAre the original data and log files still on the 7.0 server? If so, you can
reattach the original files to 7.0 using sp_attach_db. Otherwise, you'll
need to restore the 7.0 database from a 7.0 backup.
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
As I understand it a restore from version 2000 to 7 is not possible and
would require the database/objects/data to be recreated via scripts, DTS
and/or BCP.
Was there a script location that contains the schema and data files for the
upgrade? Might be able to leverage from that.
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
Optionally if you have a backup of the v7 database you could just restore
it - would be alot easier if the backup exists!
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Thanks Lori and Jerry for your quick response. Both of you have a same
solution which is to use backup. We are using veritas backup exec to backup
SQL7.0. I've been trying to restore the database to the server. For some
reason, all failed.
Yes, all of the data and log files are still on SQL 7.0 under
\mssql\data\db1_data.mdf and db1_log.ldf.
I will try Lori, reattach the db1 to see first, if it is not working, I will
come back to you.
Thanks a lot,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Hi Lori,
I tried, query:
sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
'd:\mssql7\data\db1_log.ldf'
But I got the error message saying, "I/O error (bad page id)......
connection broken.
What does this mean? Is the file corrupt?
Thanks,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
> Thanks Lori and Jerry for your quick response. Both of you have a same
> solution which is to use backup. We are using veritas backup exec to
> backup SQL7.0. I've been trying to restore the database to the server. For
> some reason, all failed.
> Yes, all of the data and log files are still on SQL 7.0 under
> \mssql\data\db1_data.mdf and db1_log.ldf.
> I will try Lori, reattach the db1 to see first, if it is not working, I
> will come back to you.
> Thanks a lot,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>|||Not sure, but usually I/O errors indicate database corruption or hardware
issues. Did you do a dbcc checkdb before you did the copy/move? Are you
sure that the files you're trying to attach are SQL 7.0 files?
"SG" <sguo@.coopervision.ca> wrote in message
news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
> 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>|||attach is only guaranteed if you actually detached the database first. Are y
ou saying that you don't
have a database backup of the 7.0 database? That you only "ripped" the datab
ase files using Veritas?
You could try creating a database on the 7.0 server with same db name and sa
me file names, stop the
SQL Server, delete the new files and copy your old files in place of the new
ones.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...[v
bcol=seagreen]
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log
.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftn
gp13.phx.gbl...
>[/vbcol]|||Hi Lori,
Yes, I'm sure that file is SQL7.0. But I forgot one thing, while I was doing
"Copy database" from 7.0 to 2k, there was an error "detach failed". I guess
that is where the problem was. Instead of copying, it did move. Before done
this database, I did a small database test, it was fine. Don't know what
happened.
Any idea?
Thanks,
Sarah
"Lori Clark" <lclark@.dbadvisor.com> wrote in message
news:uSfds42zFHA.904@.tk2msftngp13.phx.gbl...
> Not sure, but usually I/O errors indicate database corruption or hardware
> issues. Did you do a dbcc checkdb before you did the copy/move? Are you
> sure that the files you're trying to attach are SQL 7.0 files?
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>|||Hi Tibor,
I did get an error while I was copy the database about "Detach database
failed".
We have Veritas backup agent for SQL on SQL 7.0 server, it should actually
backup the database not only "ripped" the files. I might need to try your
suggestion in this case. If I create the new database, I like to use the
data file, but not the log file. Can I use new log file with the old data
file?
It turned really mess now. Does anybody have any note before I do the "copy
database wizard"? I do have another very important database needs to be
transferred from 7.0 to 2k. I cannot afford to have the same mistake.
Appreciate your idea,
Sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
> attach is only guaranteed if you actually detached the database first. Are
> you saying that you don't have a database backup of the 7.0 database? That
> you only "ripped" the database files using Veritas? You could try creating
> a database on the 7.0 server with same db name and same file names, stop
> the SQL Server, delete the new files and copy your old files in place of
> the new ones.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>
I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
(win2k) is installed. I was transferring one of the database (db1) from 7.0
to 2000 by using copy database wizard. But I found that instead of copying,
it actually moved the db1 to the new server. Since the new server is not in
production stage, I want to restore the db1 back to 7.0. I can see the data
and log files are still there. How can I have it operational again?
Please help me with this, I would greatly appreciate it.
Thanks a lot,
SarahAre the original data and log files still on the 7.0 server? If so, you can
reattach the original files to 7.0 using sp_attach_db. Otherwise, you'll
need to restore the 7.0 database from a 7.0 backup.
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
As I understand it a restore from version 2000 to 7 is not possible and
would require the database/objects/data to be recreated via scripts, DTS
and/or BCP.
Was there a script location that contains the schema and data files for the
upgrade? Might be able to leverage from that.
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||SG,
Optionally if you have a backup of the v7 database you could just restore
it - would be alot easier if the backup exists!
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Thanks Lori and Jerry for your quick response. Both of you have a same
solution which is to use backup. We are using veritas backup exec to backup
SQL7.0. I've been trying to restore the database to the server. For some
reason, all failed.
Yes, all of the data and log files are still on SQL 7.0 under
\mssql\data\db1_data.mdf and db1_log.ldf.
I will try Lori, reattach the db1 to see first, if it is not working, I will
come back to you.
Thanks a lot,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>|||Hi Lori,
I tried, query:
sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
'd:\mssql7\data\db1_log.ldf'
But I got the error message saying, "I/O error (bad page id)......
connection broken.
What does this mean? Is the file corrupt?
Thanks,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
> Thanks Lori and Jerry for your quick response. Both of you have a same
> solution which is to use backup. We are using veritas backup exec to
> backup SQL7.0. I've been trying to restore the database to the server. For
> some reason, all failed.
> Yes, all of the data and log files are still on SQL 7.0 under
> \mssql\data\db1_data.mdf and db1_log.ldf.
> I will try Lori, reattach the db1 to see first, if it is not working, I
> will come back to you.
> Thanks a lot,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>|||Not sure, but usually I/O errors indicate database corruption or hardware
issues. Did you do a dbcc checkdb before you did the copy/move? Are you
sure that the files you're trying to attach are SQL 7.0 files?
"SG" <sguo@.coopervision.ca> wrote in message
news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
> 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>|||attach is only guaranteed if you actually detached the database first. Are y
ou saying that you don't
have a database backup of the 7.0 database? That you only "ripped" the datab
ase files using Veritas?
You could try creating a database on the 7.0 server with same db name and sa
me file names, stop the
SQL Server, delete the new files and copy your old files in place of the new
ones.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...[v
bcol=seagreen]
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log
.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftn
gp13.phx.gbl...
>[/vbcol]|||Hi Lori,
Yes, I'm sure that file is SQL7.0. But I forgot one thing, while I was doing
"Copy database" from 7.0 to 2k, there was an error "detach failed". I guess
that is where the problem was. Instead of copying, it did move. Before done
this database, I did a small database test, it was fine. Don't know what
happened.
Any idea?
Thanks,
Sarah
"Lori Clark" <lclark@.dbadvisor.com> wrote in message
news:uSfds42zFHA.904@.tk2msftngp13.phx.gbl...
> Not sure, but usually I/O errors indicate database corruption or hardware
> issues. Did you do a dbcc checkdb before you did the copy/move? Are you
> sure that the files you're trying to attach are SQL 7.0 files?
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>|||Hi Tibor,
I did get an error while I was copy the database about "Detach database
failed".
We have Veritas backup agent for SQL on SQL 7.0 server, it should actually
backup the database not only "ripped" the files. I might need to try your
suggestion in this case. If I create the new database, I like to use the
data file, but not the log file. Can I use new log file with the old data
file?
It turned really mess now. Does anybody have any note before I do the "copy
database wizard"? I do have another very important database needs to be
transferred from 7.0 to 2k. I cannot afford to have the same mistake.
Appreciate your idea,
Sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
> attach is only guaranteed if you actually detached the database first. Are
> you saying that you don't have a database backup of the 7.0 database? That
> you only "ripped" the database files using Veritas? You could try creating
> a database on the 7.0 server with same db name and same file names, stop
> the SQL Server, delete the new files and copy your old files in place of
> the new ones.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>
restore database back to sql 7.0?
Hi,
I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
(win2k) is installed. I was transferring one of the database (db1) from 7.0
to 2000 by using copy database wizard. But I found that instead of copying,
it actually moved the db1 to the new server. Since the new server is not in
production stage, I want to restore the db1 back to 7.0. I can see the data
and log files are still there. How can I have it operational again?
Please help me with this, I would greatly appreciate it.
Thanks a lot,
Sarah
Are the original data and log files still on the 7.0 server? If so, you can
reattach the original files to 7.0 using sp_attach_db. Otherwise, you'll
need to restore the 7.0 database from a 7.0 backup.
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||SG,
As I understand it a restore from version 2000 to 7 is not possible and
would require the database/objects/data to be recreated via scripts, DTS
and/or BCP.
Was there a script location that contains the schema and data files for the
upgrade? Might be able to leverage from that.
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||SG,
Optionally if you have a backup of the v7 database you could just restore
it - would be alot easier if the backup exists!
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||Thanks Lori and Jerry for your quick response. Both of you have a same
solution which is to use backup. We are using veritas backup exec to backup
SQL7.0. I've been trying to restore the database to the server. For some
reason, all failed.
Yes, all of the data and log files are still on SQL 7.0 under
\mssql\data\db1_data.mdf and db1_log.ldf.
I will try Lori, reattach the db1 to see first, if it is not working, I will
come back to you.
Thanks a lot,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||Hi Lori,
I tried, query:
sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
'd:\mssql7\data\db1_log.ldf'
But I got the error message saying, "I/O error (bad page id)......
connection broken.
What does this mean? Is the file corrupt?
Thanks,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
> Thanks Lori and Jerry for your quick response. Both of you have a same
> solution which is to use backup. We are using veritas backup exec to
> backup SQL7.0. I've been trying to restore the database to the server. For
> some reason, all failed.
> Yes, all of the data and log files are still on SQL 7.0 under
> \mssql\data\db1_data.mdf and db1_log.ldf.
> I will try Lori, reattach the db1 to see first, if it is not working, I
> will come back to you.
> Thanks a lot,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>
|||Not sure, but usually I/O errors indicate database corruption or hardware
issues. Did you do a dbcc checkdb before you did the copy/move? Are you
sure that the files you're trying to attach are SQL 7.0 files?
"SG" <sguo@.coopervision.ca> wrote in message
news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
> 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>
|||attach is only guaranteed if you actually detached the database first. Are you saying that you don't
have a database backup of the 7.0 database? That you only "ripped" the database files using Veritas?
You could try creating a database on the 7.0 server with same db name and same file names, stop the
SQL Server, delete the new files and copy your old files in place of the new ones.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>
|||Hi Lori,
Yes, I'm sure that file is SQL7.0. But I forgot one thing, while I was doing
"Copy database" from 7.0 to 2k, there was an error "detach failed". I guess
that is where the problem was. Instead of copying, it did move. Before done
this database, I did a small database test, it was fine. Don't know what
happened.
Any idea?
Thanks,
Sarah
"Lori Clark" <lclark@.dbadvisor.com> wrote in message
news:uSfds42zFHA.904@.tk2msftngp13.phx.gbl...
> Not sure, but usually I/O errors indicate database corruption or hardware
> issues. Did you do a dbcc checkdb before you did the copy/move? Are you
> sure that the files you're trying to attach are SQL 7.0 files?
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>
|||Hi Tibor,
I did get an error while I was copy the database about "Detach database
failed".
We have Veritas backup agent for SQL on SQL 7.0 server, it should actually
backup the database not only "ripped" the files. I might need to try your
suggestion in this case. If I create the new database, I like to use the
data file, but not the log file. Can I use new log file with the old data
file?
It turned really mess now. Does anybody have any note before I do the "copy
database wizard"? I do have another very important database needs to be
transferred from 7.0 to 2k. I cannot afford to have the same mistake.
Appreciate your idea,
Sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
> attach is only guaranteed if you actually detached the database first. Are
> you saying that you don't have a database backup of the 7.0 database? That
> you only "ripped" the database files using Veritas? You could try creating
> a database on the 7.0 server with same db name and same file names, stop
> the SQL Server, delete the new files and copy your old files in place of
> the new ones.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>
I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
(win2k) is installed. I was transferring one of the database (db1) from 7.0
to 2000 by using copy database wizard. But I found that instead of copying,
it actually moved the db1 to the new server. Since the new server is not in
production stage, I want to restore the db1 back to 7.0. I can see the data
and log files are still there. How can I have it operational again?
Please help me with this, I would greatly appreciate it.
Thanks a lot,
Sarah
Are the original data and log files still on the 7.0 server? If so, you can
reattach the original files to 7.0 using sp_attach_db. Otherwise, you'll
need to restore the 7.0 database from a 7.0 backup.
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||SG,
As I understand it a restore from version 2000 to 7 is not possible and
would require the database/objects/data to be recreated via scripts, DTS
and/or BCP.
Was there a script location that contains the schema and data files for the
upgrade? Might be able to leverage from that.
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||SG,
Optionally if you have a backup of the v7 database you could just restore
it - would be alot easier if the backup exists!
HTH
Jerry
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||Thanks Lori and Jerry for your quick response. Both of you have a same
solution which is to use backup. We are using veritas backup exec to backup
SQL7.0. I've been trying to restore the database to the server. For some
reason, all failed.
Yes, all of the data and log files are still on SQL 7.0 under
\mssql\data\db1_data.mdf and db1_log.ldf.
I will try Lori, reattach the db1 to see first, if it is not working, I will
come back to you.
Thanks a lot,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have a SQL7.0 (NT4) with all the databases. Recently a new SQL 2000
> (win2k) is installed. I was transferring one of the database (db1) from
> 7.0 to 2000 by using copy database wizard. But I found that instead of
> copying, it actually moved the db1 to the new server. Since the new server
> is not in production stage, I want to restore the db1 back to 7.0. I can
> see the data and log files are still there. How can I have it operational
> again?
> Please help me with this, I would greatly appreciate it.
> Thanks a lot,
> Sarah
>
|||Hi Lori,
I tried, query:
sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
'd:\mssql7\data\db1_log.ldf'
But I got the error message saying, "I/O error (bad page id)......
connection broken.
What does this mean? Is the file corrupt?
Thanks,
Sarah
"SG" <sguo@.coopervision.ca> wrote in message
news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
> Thanks Lori and Jerry for your quick response. Both of you have a same
> solution which is to use backup. We are using veritas backup exec to
> backup SQL7.0. I've been trying to restore the database to the server. For
> some reason, all failed.
> Yes, all of the data and log files are still on SQL 7.0 under
> \mssql\data\db1_data.mdf and db1_log.ldf.
> I will try Lori, reattach the db1 to see first, if it is not working, I
> will come back to you.
> Thanks a lot,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:Oc5Dmw0zFHA.1252@.TK2MSFTNGP09.phx.gbl...
>
|||Not sure, but usually I/O errors indicate database corruption or hardware
issues. Did you do a dbcc checkdb before you did the copy/move? Are you
sure that the files you're trying to attach are SQL 7.0 files?
"SG" <sguo@.coopervision.ca> wrote in message
news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf',
> 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message
> news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>
|||attach is only guaranteed if you actually detached the database first. Are you saying that you don't
have a database backup of the 7.0 database? That you only "ripped" the database files using Veritas?
You could try creating a database on the 7.0 server with same db name and same file names, stop the
SQL Server, delete the new files and copy your old files in place of the new ones.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SG" <sguo@.coopervision.ca> wrote in message news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
> Hi Lori,
> I tried, query:
> sp_attach_db 'db1', 'd:\mssql7\data\db1_data.mdf', 'd:\mssql7\data\db1_log.ldf'
> But I got the error message saying, "I/O error (bad page id)......
> connection broken.
> What does this mean? Is the file corrupt?
> Thanks,
> Sarah
> "SG" <sguo@.coopervision.ca> wrote in message news:uZMVgA1zFHA.908@.tk2msftngp13.phx.gbl...
>
|||Hi Lori,
Yes, I'm sure that file is SQL7.0. But I forgot one thing, while I was doing
"Copy database" from 7.0 to 2k, there was an error "detach failed". I guess
that is where the problem was. Instead of copying, it did move. Before done
this database, I did a small database test, it was fine. Don't know what
happened.
Any idea?
Thanks,
Sarah
"Lori Clark" <lclark@.dbadvisor.com> wrote in message
news:uSfds42zFHA.904@.tk2msftngp13.phx.gbl...
> Not sure, but usually I/O errors indicate database corruption or hardware
> issues. Did you do a dbcc checkdb before you did the copy/move? Are you
> sure that the files you're trying to attach are SQL 7.0 files?
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>
|||Hi Tibor,
I did get an error while I was copy the database about "Detach database
failed".
We have Veritas backup agent for SQL on SQL 7.0 server, it should actually
backup the database not only "ripped" the files. I might need to try your
suggestion in this case. If I create the new database, I like to use the
data file, but not the log file. Can I use new log file with the old data
file?
It turned really mess now. Does anybody have any note before I do the "copy
database wizard"? I do have another very important database needs to be
transferred from 7.0 to 2k. I cannot afford to have the same mistake.
Appreciate your idea,
Sarah
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:Oa3uJ67zFHA.464@.TK2MSFTNGP15.phx.gbl...
> attach is only guaranteed if you actually detached the database first. Are
> you saying that you don't have a database backup of the 7.0 database? That
> you only "ripped" the database files using Veritas? You could try creating
> a database on the 7.0 server with same db name and same file names, stop
> the SQL Server, delete the new files and copy your old files in place of
> the new ones.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "SG" <sguo@.coopervision.ca> wrote in message
> news:e4bFrp2zFHA.3180@.TK2MSFTNGP14.phx.gbl...
>
Tuesday, March 20, 2012
Restore Database
Hello, him story my problem, we had a problem with the server where was installed the sqlserver2005, we do not have backups, nevertheless we could recover the files data.mdf and log.ldf of the database, like I can carry out a restore utilizing these files?
No, you do NOT need to RESTORE with those two files.
You need to ATTACH the files. Check in Books Online about using ATTACH.
Friday, March 9, 2012
Restore access for sql service accounts
Hello,
due to massive errors on one server having SQL 2005 installed, I was forced
to reset the group policies to initial settings (installation settings) usin
g
the gpo fix command of the support tools.
Unfortunately, all service accounts of sql are not running anylonger, I
assume the ahtorisation was reset to an initial value I don't know of.
Is there any tool available or repair functionalty available which will
reset the initial sql server account policies which will be installed during
SQL 2005 setup?
Yours
StephanHi Stephan.
SQL Server grant the need rights when you change the service account, so the
easiest way is to change services to start with the LocalService account an
then, change them again to the service accounts.
Regards
Antonio Soto
Solid Quality Learning
http://www.sqlu.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Stephan Hofmann" <StephanHofmann@.discussions.microsoft.com> escribi en el
mensaje news:44568C5E-D332-4F77-BB66-02BA8BDD47A7@.microsoft.com...
> Hello,
> due to massive errors on one server having SQL 2005 installed, I was
> forced
> to reset the group policies to initial settings (installation settings)
> using
> the gpo fix command of the support tools.
> Unfortunately, all service accounts of sql are not running anylonger, I
> assume the ahtorisation was reset to an initial value I don't know of.
> Is there any tool available or repair functionalty available which will
> reset the initial sql server account policies which will be installed
> during
> SQL 2005 setup?
> Yours
> Stephan|||Hello,
I have changed to localservice account, started the service, the service was
able to launch and finally I have set back to the previous service account.
Nothing changed.
I still believe the authorisation has changed for my preconfigured service
accounts.
By the way: the MSSQLADhelper service cannot be launched as well, is coming
with an other error. I don't know if this service has to run or not. If yes,
is there any issue known and reported? Thsi service is also not running on
another local SQL installation but there the SQL database is running using
local computer accounts (not LocalService). I don't know the dependencies of
service MSSQLadhelper.
Yours
Stephan
"Antonio Soto" wrote:
> Hi Stephan.
> SQL Server grant the need rights when you change the service account, so t
he
> easiest way is to change services to start with the LocalService account a
n
> then, change them again to the service accounts.
> Regards
>
> --
> Antonio Soto
> Solid Quality Learning
> http://www.sqlu.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
> "Stephan Hofmann" <StephanHofmann@.discussions.microsoft.com> escribió en
el
> mensaje news:44568C5E-D332-4F77-BB66-02BA8BDD47A7@.microsoft.com...
>
>|||You don't run MSSQLServerADHelper. Leave start up type set
to manual and running state at stopped - SQL Server does
the rest. The ADHelper service runs when requested to by SQL
Server service or Analysis Server service and then stops the
service when it has completed its work.
-Sue
On Tue, 11 Apr 2006 13:21:03 -0700, Stephan Hofmann
<StephanHofmann@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hello,
>I have changed to localservice account, started the service, the service wa
s
>able to launch and finally I have set back to the previous service account.
>Nothing changed.
>I still believe the authorisation has changed for my preconfigured service
>accounts.
>By the way: the MSSQLADhelper service cannot be launched as well, is coming
>with an other error. I don't know if this service has to run or not. If yes
,
>is there any issue known and reported? Thsi service is also not running on
>another local SQL installation but there the SQL database is running using
>local computer accounts (not LocalService). I don't know the dependencies o
f
>service MSSQLadhelper.
>
>Yours
>Stephan
>
>"Antonio Soto" wrote:
>|||Hello,
thanks for the good hint. Ok, I have changed nothing on ADhelper but what's
about my origin problem around the unability to launch any service account
with domain user accounts? How can I reestablish the service accounts? Are
there policies / Security settings which can be reset by a tool? What can I
check on my side to scope the error? (something like a check list?)
Thanks
Stephan.|||X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.sqlserver.security
NNTP-Posting-Host: c-71-56-205-87.hsd1.co.comcast.net 71.56.205.87
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Lines: 1
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.sqlserver.security:28281
The necessary permissions, rights for service accounts are
listed in the following article:
How to change the SQL Server or SQL Server Agent service
account without using SQL Enterprise Manager in SQL Server
2000 or SQL Server Management Studio in SQL Server 2005
http://support.microsoft.com/?id=283811
-Sue
On Wed, 12 Apr 2006 01:21:01 -0700, Stephan Hofmann
<StephanHofmann@.discussions.microsoft.com> wrote:
>Hello,
>thanks for the good hint. Ok, I have changed nothing on ADhelper but what's
>about my origin problem around the unability to launch any service account
>with domain user accounts? How can I reestablish the service accounts? Are
>there policies / Security settings which can be reset by a tool? What can I
>check on my side to scope the error? (something like a check list?)
>Thanks
>Stephan.
due to massive errors on one server having SQL 2005 installed, I was forced
to reset the group policies to initial settings (installation settings) usin
g
the gpo fix command of the support tools.
Unfortunately, all service accounts of sql are not running anylonger, I
assume the ahtorisation was reset to an initial value I don't know of.
Is there any tool available or repair functionalty available which will
reset the initial sql server account policies which will be installed during
SQL 2005 setup?
Yours
StephanHi Stephan.
SQL Server grant the need rights when you change the service account, so the
easiest way is to change services to start with the LocalService account an
then, change them again to the service accounts.
Regards
Antonio Soto
Solid Quality Learning
http://www.sqlu.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Stephan Hofmann" <StephanHofmann@.discussions.microsoft.com> escribi en el
mensaje news:44568C5E-D332-4F77-BB66-02BA8BDD47A7@.microsoft.com...
> Hello,
> due to massive errors on one server having SQL 2005 installed, I was
> forced
> to reset the group policies to initial settings (installation settings)
> using
> the gpo fix command of the support tools.
> Unfortunately, all service accounts of sql are not running anylonger, I
> assume the ahtorisation was reset to an initial value I don't know of.
> Is there any tool available or repair functionalty available which will
> reset the initial sql server account policies which will be installed
> during
> SQL 2005 setup?
> Yours
> Stephan|||Hello,
I have changed to localservice account, started the service, the service was
able to launch and finally I have set back to the previous service account.
Nothing changed.
I still believe the authorisation has changed for my preconfigured service
accounts.
By the way: the MSSQLADhelper service cannot be launched as well, is coming
with an other error. I don't know if this service has to run or not. If yes,
is there any issue known and reported? Thsi service is also not running on
another local SQL installation but there the SQL database is running using
local computer accounts (not LocalService). I don't know the dependencies of
service MSSQLadhelper.
Yours
Stephan
"Antonio Soto" wrote:
> Hi Stephan.
> SQL Server grant the need rights when you change the service account, so t
he
> easiest way is to change services to start with the LocalService account a
n
> then, change them again to the service accounts.
> Regards
>
> --
> Antonio Soto
> Solid Quality Learning
> http://www.sqlu.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
> "Stephan Hofmann" <StephanHofmann@.discussions.microsoft.com> escribió en
el
> mensaje news:44568C5E-D332-4F77-BB66-02BA8BDD47A7@.microsoft.com...
>
>|||You don't run MSSQLServerADHelper. Leave start up type set
to manual and running state at stopped - SQL Server does
the rest. The ADHelper service runs when requested to by SQL
Server service or Analysis Server service and then stops the
service when it has completed its work.
-Sue
On Tue, 11 Apr 2006 13:21:03 -0700, Stephan Hofmann
<StephanHofmann@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hello,
>I have changed to localservice account, started the service, the service wa
s
>able to launch and finally I have set back to the previous service account.
>Nothing changed.
>I still believe the authorisation has changed for my preconfigured service
>accounts.
>By the way: the MSSQLADhelper service cannot be launched as well, is coming
>with an other error. I don't know if this service has to run or not. If yes
,
>is there any issue known and reported? Thsi service is also not running on
>another local SQL installation but there the SQL database is running using
>local computer accounts (not LocalService). I don't know the dependencies o
f
>service MSSQLadhelper.
>
>Yours
>Stephan
>
>"Antonio Soto" wrote:
>|||Hello,
thanks for the good hint. Ok, I have changed nothing on ADhelper but what's
about my origin problem around the unability to launch any service account
with domain user accounts? How can I reestablish the service accounts? Are
there policies / Security settings which can be reset by a tool? What can I
check on my side to scope the error? (something like a check list?)
Thanks
Stephan.|||X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.sqlserver.security
NNTP-Posting-Host: c-71-56-205-87.hsd1.co.comcast.net 71.56.205.87
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Lines: 1
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.sqlserver.security:28281
The necessary permissions, rights for service accounts are
listed in the following article:
How to change the SQL Server or SQL Server Agent service
account without using SQL Enterprise Manager in SQL Server
2000 or SQL Server Management Studio in SQL Server 2005
http://support.microsoft.com/?id=283811
-Sue
On Wed, 12 Apr 2006 01:21:01 -0700, Stephan Hofmann
<StephanHofmann@.discussions.microsoft.com> wrote:
>Hello,
>thanks for the good hint. Ok, I have changed nothing on ADhelper but what's
>about my origin problem around the unability to launch any service account
>with domain user accounts? How can I reestablish the service accounts? Are
>there policies / Security settings which can be reset by a tool? What can I
>check on my side to scope the error? (something like a check list?)
>Thanks
>Stephan.
Saturday, February 25, 2012
Restore 2005 to 2000 Database
The machine I do development on has SQL Server 2005 installed.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
How can I restore a SQL Server 2005 database to a SQL Server 2000 database?
You can not restore or attach a sql2005 db to sql2000.
You would need to export all the data, then import it back.|||That's pretty inconvenient!
Thanks for you help.
|||Ugh, that's awful. Way to make our lives hard, microsoft!
|||
At least the opposit is working!
So take a SQL Server 7, 2000 backup and restore it to a SQL Server 2005 Server. That is not true for master, model, msdb, but user database should work fine.
For doing the restore one has to use the option MOVE
|||I successfully attached a SQL 2005 database back into SQL 2000. However, that SQL 2005 database was originally from SQL 2000 and its compatibility was set to 80.
|||It's very interesting. Have you occured this error?:
Error 602: Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
We tried to attach our database back to SQL 2000, but this error occured.
|||The datadictonairy has changed completely. I think you should export all application tables in SQL Server 2000 and import them in SQL Server 2000. Be aware of the relationships :-)|||I'll say. That just happened to me also. the database grew from 32gigs to 72gigs since we installed 2005. We only need 2000 to migrate our data to a new version of the software we are using. Test it on 2005 in a test databse for a couple of weeks, then do it all over again for production database. errrrrr..|||You're asking to restore a much newer version of a database backup into an older versiion of the product. How can you possible expect this to work?
Would you expect Windows XP to run on an XT (Intel 8086) system? Of course not! So why expect the same here?
Your best option is to export the data.
Besides, who in their right mind develops something on a system that does not replicate their customers environment? Sounds like you haven't been in the game for long.
|||hi there
i'm facing the same problem...
1] I had SQL 2000 database dbTest...
2] attached that dbTest.mdf to sql 2005
3] now when trying to attach that same .mdf to sql 2000, i'm getting following error --
Error 602: Could not find row in sysindexes for database ID 9, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can u please tell me how did u get ur error solved? Its a bit urgent...
Thanks in Advance!!
|||it is possible when you export the data from sql2005 then import to SQL 2000. An alternative method for this is to create 2 named instances within same computer. 1 for SQL 2005 and 1 for SQL 2000 on the same server.
Then export DB from SQL2005 to SQL2000. Afterwards backup your database in SQL2000.
It worked for me.. Yes i agree its a kind of catching the ear by a long way. But its better than it's not working.
I am not sure if Microsoft has announced backward compability of SQL 2005 Db's or supplied a detailed "How to" instruction or not; but they should have "SHOUT IT OUT LOUD" else this brings people anger when Microsoft emancipates itself like "We dont have to supply this compability"
So that; i'm in anger...
|||My view on this is that exporting from 2005 to 2000 is pretty easy using the export feature in 2005.
While I don't disagree with the view that you should develop on the same technology as your clients, I think most developers see SQL/Server as a collection of tables, views, indexes, relationships, i.e. not particulary using new features from SQL/Server 2005, so its pretty inconvenient not knowing how to do this, and for mixed client environments where some databases are 2005, others 2000, its essential.
Selecting export in 2005 and choosing all the objects, for me worked ok. If I had used a new feature in 2005 then fair enough, but I would not be wanting to export back to 2000 in this circumstance.
|||It makes me so frustrated!! I like to keep up to date, plus my old dev machine is getting on in years, so I splash out on a new PC with Vista, only to find I can't install SQL 2000 and am forced to use SQL 2005. I set everything up, make some changes to the database for my web app, then find I can't update the database on my web host's server because they're still on SQL 2000! I have no alternative but to run SQL 2000 on the old PC.
People ready!! my arse!
Restore 2005 to 2000 Database
The machine I do development on has SQL Server 2005 installed.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
How can I restore a SQL Server 2005 database to a SQL Server 2000 database?You can not restore or attach a sql2005 db to sql2000.
You would need to export all the data, then import it back.|||That's pretty inconvenient!
Thanks for you help.|||Ugh, that's awful. Way to make our lives hard, microsoft!|||
At least the opposit is working!
So take a SQL Server 7, 2000 backup and restore it to a SQL Server 2005 Server. That is not true for master, model, msdb, but user database should work fine.
For doing the restore one has to use the option MOVE
|||I successfully attached a SQL 2005 database back into SQL 2000. However, that SQL 2005 database was originally from SQL 2000 and its compatibility was set to 80.
|||
It's very interesting. Have you occured this error?:
Error 602: Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
We tried to attach our database back to SQL 2000, but this error occured.
|||The datadictonairy has changed completely. I think you should export all application tables in SQL Server 2000 and import them in SQL Server 2000. Be aware of the relationships :-)|||I'll say. That just happened to me also. the database grew from 32gigs to 72gigs since we installed 2005. We only need 2000 to migrate our data to a new version of the software we are using. Test it on 2005 in a test databse for a couple of weeks, then do it all over again for production database. errrrrr..|||You're asking to restore a much newer version of a database backup into an older versiion of the product. How can you possible expect this to work?
Would you expect Windows XP to run on an XT (Intel 8086) system? Of course not! So why expect the same here?
Your best option is to export the data.
Besides, who in their right mind develops something on a system that does not replicate their customers environment? Sounds like you haven't been in the game for long.
|||hi there
i'm facing the same problem...
1] I had SQL 2000 database dbTest...
2] attached that dbTest.mdf to sql 2005
3] now when trying to attach that same .mdf to sql 2000, i'm getting following error --
Error 602: Could not find row in sysindexes for database ID 9, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can u please tell me how did u get ur error solved? Its a bit urgent...
Thanks in Advance!!
|||it is possible when you export the data from sql2005 then import to SQL 2000. An alternative method for this is to create 2 named instances within same computer. 1 for SQL 2005 and 1 for SQL 2000 on the same server.
Then export DB from SQL2005 to SQL2000. Afterwards backup your database in SQL2000.
It worked for me.. Yes i agree its a kind of catching the ear by a long way. But its better than it's not working.
I am not sure if Microsoft has announced backward compability of SQL 2005 Db's or supplied a detailed "How to" instruction or not; but they should have "SHOUT IT OUT LOUD" else this brings people anger when Microsoft emancipates itself like "We dont have to supply this compability"
So that; i'm in anger...
|||
My view on this is that exporting from 2005 to 2000 is pretty easy using the export feature in 2005.
While I don't disagree with the view that you should develop on the same technology as your clients, I think most developers see SQL/Server as a collection of tables, views, indexes, relationships, i.e. not particulary using new features from SQL/Server 2005, so its pretty inconvenient not knowing how to do this, and for mixed client environments where some databases are 2005, others 2000, its essential.
Selecting export in 2005 and choosing all the objects, for me worked ok. If I had used a new feature in 2005 then fair enough, but I would not be wanting to export back to 2000 in this circumstance.
|||It makes me so frustrated!! I like to keep up to date, plus my old dev machine is getting on in years, so I splash out on a new PC with Vista, only to find I can't install SQL 2000 and am forced to use SQL 2005. I set everything up, make some changes to the database for my web app, then find I can't update the database on my web host's server because they're still on SQL 2000! I have no alternative but to run SQL 2000 on the old PC.
People ready!! my arse!
Restore 2005 to 2000 Database
The machine I do development on has SQL Server 2005 installed.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
How can I restore a SQL Server 2005 database to a SQL Server 2000 database?You can not restore or attach a sql2005 db to sql2000.
You would need to export all the data, then import it back.|||That's pretty inconvenient!
Thanks for you help.|||Ugh, that's awful. Way to make our lives hard, microsoft!|||
At least the opposit is working!
So take a SQL Server 7, 2000 backup and restore it to a SQL Server 2005 Server. That is not true for master, model, msdb, but user database should work fine.
For doing the restore one has to use the option MOVE
|||I successfully attached a SQL 2005 database back into SQL 2000. However, that SQL 2005 database was originally from SQL 2000 and its compatibility was set to 80.
|||
It's very interesting. Have you occured this error?:
Error 602: Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
We tried to attach our database back to SQL 2000, but this error occured.
|||The datadictonairy has changed completely. I think you should export all application tables in SQL Server 2000 and import them in SQL Server 2000. Be aware of the relationships :-)|||I'll say. That just happened to me also. the database grew from 32gigs to 72gigs since we installed 2005. We only need 2000 to migrate our data to a new version of the software we are using. Test it on 2005 in a test databse for a couple of weeks, then do it all over again for production database. errrrrr..|||You're asking to restore a much newer version of a database backup into an older versiion of the product. How can you possible expect this to work?
Would you expect Windows XP to run on an XT (Intel 8086) system? Of course not! So why expect the same here?
Your best option is to export the data.
Besides, who in their right mind develops something on a system that does not replicate their customers environment? Sounds like you haven't been in the game for long.
|||hi there
i'm facing the same problem...
1] I had SQL 2000 database dbTest...
2] attached that dbTest.mdf to sql 2005
3] now when trying to attach that same .mdf to sql 2000, i'm getting following error --
Error 602: Could not find row in sysindexes for database ID 9, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can u please tell me how did u get ur error solved? Its a bit urgent...
Thanks in Advance!!
|||it is possible when you export the data from sql2005 then import to SQL 2000. An alternative method for this is to create 2 named instances within same computer. 1 for SQL 2005 and 1 for SQL 2000 on the same server.
Then export DB from SQL2005 to SQL2000. Afterwards backup your database in SQL2000.
It worked for me.. Yes i agree its a kind of catching the ear by a long way. But its better than it's not working.
I am not sure if Microsoft has announced backward compability of SQL 2005 Db's or supplied a detailed "How to" instruction or not; but they should have "SHOUT IT OUT LOUD" else this brings people anger when Microsoft emancipates itself like "We dont have to supply this compability"
So that; i'm in anger...
|||
My view on this is that exporting from 2005 to 2000 is pretty easy using the export feature in 2005.
While I don't disagree with the view that you should develop on the same technology as your clients, I think most developers see SQL/Server as a collection of tables, views, indexes, relationships, i.e. not particulary using new features from SQL/Server 2005, so its pretty inconvenient not knowing how to do this, and for mixed client environments where some databases are 2005, others 2000, its essential.
Selecting export in 2005 and choosing all the objects, for me worked ok. If I had used a new feature in 2005 then fair enough, but I would not be wanting to export back to 2000 in this circumstance.
|||It makes me so frustrated!! I like to keep up to date, plus my old dev machine is getting on in years, so I splash out on a new PC with Vista, only to find I can't install SQL 2000 and am forced to use SQL 2005. I set everything up, make some changes to the database for my web app, then find I can't update the database on my web host's server because they're still on SQL 2000! I have no alternative but to run SQL 2000 on the old PC.
People ready!! my arse!
Restore 2005 to 2000 Database
The machine I do development on has SQL Server 2005 installed.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
How can I restore a SQL Server 2005 database to a SQL Server 2000 database?
You can not restore or attach a sql2005 db to sql2000.
You would need to export all the data, then import it back.|||That's pretty inconvenient!
Thanks for you help.
|||Ugh, that's awful. Way to make our lives hard, microsoft!
|||
At least the opposit is working!
So take a SQL Server 7, 2000 backup and restore it to a SQL Server 2005 Server. That is not true for master, model, msdb, but user database should work fine.
For doing the restore one has to use the option MOVE
|||I successfully attached a SQL 2005 database back into SQL 2000. However, that SQL 2005 database was originally from SQL 2000 and its compatibility was set to 80.
|||It's very interesting. Have you occured this error?:
Error 602: Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
We tried to attach our database back to SQL 2000, but this error occured.
|||The datadictonairy has changed completely. I think you should export all application tables in SQL Server 2000 and import them in SQL Server 2000. Be aware of the relationships :-)|||I'll say. That just happened to me also. the database grew from 32gigs to 72gigs since we installed 2005. We only need 2000 to migrate our data to a new version of the software we are using. Test it on 2005 in a test databse for a couple of weeks, then do it all over again for production database. errrrrr..|||You're asking to restore a much newer version of a database backup into an older versiion of the product. How can you possible expect this to work?
Would you expect Windows XP to run on an XT (Intel 8086) system? Of course not! So why expect the same here?
Your best option is to export the data.
Besides, who in their right mind develops something on a system that does not replicate their customers environment? Sounds like you haven't been in the game for long.
|||hi there
i'm facing the same problem...
1] I had SQL 2000 database dbTest...
2] attached that dbTest.mdf to sql 2005
3] now when trying to attach that same .mdf to sql 2000, i'm getting following error --
Error 602: Could not find row in sysindexes for database ID 9, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can u please tell me how did u get ur error solved? Its a bit urgent...
Thanks in Advance!!
|||it is possible when you export the data from sql2005 then import to SQL 2000. An alternative method for this is to create 2 named instances within same computer. 1 for SQL 2005 and 1 for SQL 2000 on the same server.
Then export DB from SQL2005 to SQL2000. Afterwards backup your database in SQL2000.
It worked for me.. Yes i agree its a kind of catching the ear by a long way. But its better than it's not working.
I am not sure if Microsoft has announced backward compability of SQL 2005 Db's or supplied a detailed "How to" instruction or not; but they should have "SHOUT IT OUT LOUD" else this brings people anger when Microsoft emancipates itself like "We dont have to supply this compability"
So that; i'm in anger...
|||My view on this is that exporting from 2005 to 2000 is pretty easy using the export feature in 2005.
While I don't disagree with the view that you should develop on the same technology as your clients, I think most developers see SQL/Server as a collection of tables, views, indexes, relationships, i.e. not particulary using new features from SQL/Server 2005, so its pretty inconvenient not knowing how to do this, and for mixed client environments where some databases are 2005, others 2000, its essential.
Selecting export in 2005 and choosing all the objects, for me worked ok. If I had used a new feature in 2005 then fair enough, but I would not be wanting to export back to 2000 in this circumstance.
|||It makes me so frustrated!! I like to keep up to date, plus my old dev machine is getting on in years, so I splash out on a new PC with Vista, only to find I can't install SQL 2000 and am forced to use SQL 2005. I set everything up, make some changes to the database for my web app, then find I can't update the database on my web host's server because they're still on SQL 2000! I have no alternative but to run SQL 2000 on the old PC.
People ready!! my arse!
Restore 2005 to 2000 Database
The machine I do development on has SQL Server 2005 installed.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
How can I restore a SQL Server 2005 database to a SQL Server 2000 database?
You can not restore or attach a sql2005 db to sql2000.
You would need to export all the data, then import it back.|||That's pretty inconvenient!
Thanks for you help.
|||Ugh, that's awful. Way to make our lives hard, microsoft!
|||
At least the opposit is working!
So take a SQL Server 7, 2000 backup and restore it to a SQL Server 2005 Server. That is not true for master, model, msdb, but user database should work fine.
For doing the restore one has to use the option MOVE
|||I successfully attached a SQL 2005 database back into SQL 2000. However, that SQL 2005 database was originally from SQL 2000 and its compatibility was set to 80.
|||It's very interesting. Have you occured this error?:
Error 602: Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
We tried to attach our database back to SQL 2000, but this error occured.
|||The datadictonairy has changed completely. I think you should export all application tables in SQL Server 2000 and import them in SQL Server 2000. Be aware of the relationships :-)|||I'll say. That just happened to me also. the database grew from 32gigs to 72gigs since we installed 2005. We only need 2000 to migrate our data to a new version of the software we are using. Test it on 2005 in a test databse for a couple of weeks, then do it all over again for production database. errrrrr..|||You're asking to restore a much newer version of a database backup into an older versiion of the product. How can you possible expect this to work?
Would you expect Windows XP to run on an XT (Intel 8086) system? Of course not! So why expect the same here?
Your best option is to export the data.
Besides, who in their right mind develops something on a system that does not replicate their customers environment? Sounds like you haven't been in the game for long.
|||hi there
i'm facing the same problem...
1] I had SQL 2000 database dbTest...
2] attached that dbTest.mdf to sql 2005
3] now when trying to attach that same .mdf to sql 2000, i'm getting following error --
Error 602: Could not find row in sysindexes for database ID 9, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can u please tell me how did u get ur error solved? Its a bit urgent...
Thanks in Advance!!
|||it is possible when you export the data from sql2005 then import to SQL 2000. An alternative method for this is to create 2 named instances within same computer. 1 for SQL 2005 and 1 for SQL 2000 on the same server.
Then export DB from SQL2005 to SQL2000. Afterwards backup your database in SQL2000.
It worked for me.. Yes i agree its a kind of catching the ear by a long way. But its better than it's not working.
I am not sure if Microsoft has announced backward compability of SQL 2005 Db's or supplied a detailed "How to" instruction or not; but they should have "SHOUT IT OUT LOUD" else this brings people anger when Microsoft emancipates itself like "We dont have to supply this compability"
So that; i'm in anger...
|||My view on this is that exporting from 2005 to 2000 is pretty easy using the export feature in 2005.
While I don't disagree with the view that you should develop on the same technology as your clients, I think most developers see SQL/Server as a collection of tables, views, indexes, relationships, i.e. not particulary using new features from SQL/Server 2005, so its pretty inconvenient not knowing how to do this, and for mixed client environments where some databases are 2005, others 2000, its essential.
Selecting export in 2005 and choosing all the objects, for me worked ok. If I had used a new feature in 2005 then fair enough, but I would not be wanting to export back to 2000 in this circumstance.
|||It makes me so frustrated!! I like to keep up to date, plus my old dev machine is getting on in years, so I splash out on a new PC with Vista, only to find I can't install SQL 2000 and am forced to use SQL 2005. I set everything up, make some changes to the database for my web app, then find I can't update the database on my web host's server because they're still on SQL 2000! I have no alternative but to run SQL 2000 on the old PC.
People ready!! my arse!
Restore 2005 to 2000 Database
The machine I do development on has SQL Server 2005 installed.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
How can I restore a SQL Server 2005 database to a SQL Server 2000 database?
You can not restore or attach a sql2005 db to sql2000.
You would need to export all the data, then import it back.|||That's pretty inconvenient!
Thanks for you help.
|||Ugh, that's awful. Way to make our lives hard, microsoft!
|||
At least the opposit is working!
So take a SQL Server 7, 2000 backup and restore it to a SQL Server 2005 Server. That is not true for master, model, msdb, but user database should work fine.
For doing the restore one has to use the option MOVE
|||I successfully attached a SQL 2005 database back into SQL 2000. However, that SQL 2005 database was originally from SQL 2000 and its compatibility was set to 80.
|||It's very interesting. Have you occured this error?:
Error 602: Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
We tried to attach our database back to SQL 2000, but this error occured.
|||The datadictonairy has changed completely. I think you should export all application tables in SQL Server 2000 and import them in SQL Server 2000. Be aware of the relationships :-)|||I'll say. That just happened to me also. the database grew from 32gigs to 72gigs since we installed 2005. We only need 2000 to migrate our data to a new version of the software we are using. Test it on 2005 in a test databse for a couple of weeks, then do it all over again for production database. errrrrr..|||You're asking to restore a much newer version of a database backup into an older versiion of the product. How can you possible expect this to work?
Would you expect Windows XP to run on an XT (Intel 8086) system? Of course not! So why expect the same here?
Your best option is to export the data.
Besides, who in their right mind develops something on a system that does not replicate their customers environment? Sounds like you haven't been in the game for long.
|||hi there
i'm facing the same problem...
1] I had SQL 2000 database dbTest...
2] attached that dbTest.mdf to sql 2005
3] now when trying to attach that same .mdf to sql 2000, i'm getting following error --
Error 602: Could not find row in sysindexes for database ID 9, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can u please tell me how did u get ur error solved? Its a bit urgent...
Thanks in Advance!!
|||it is possible when you export the data from sql2005 then import to SQL 2000. An alternative method for this is to create 2 named instances within same computer. 1 for SQL 2005 and 1 for SQL 2000 on the same server.
Then export DB from SQL2005 to SQL2000. Afterwards backup your database in SQL2000.
It worked for me.. Yes i agree its a kind of catching the ear by a long way. But its better than it's not working.
I am not sure if Microsoft has announced backward compability of SQL 2005 Db's or supplied a detailed "How to" instruction or not; but they should have "SHOUT IT OUT LOUD" else this brings people anger when Microsoft emancipates itself like "We dont have to supply this compability"
So that; i'm in anger...
|||My view on this is that exporting from 2005 to 2000 is pretty easy using the export feature in 2005.
While I don't disagree with the view that you should develop on the same technology as your clients, I think most developers see SQL/Server as a collection of tables, views, indexes, relationships, i.e. not particulary using new features from SQL/Server 2005, so its pretty inconvenient not knowing how to do this, and for mixed client environments where some databases are 2005, others 2000, its essential.
Selecting export in 2005 and choosing all the objects, for me worked ok. If I had used a new feature in 2005 then fair enough, but I would not be wanting to export back to 2000 in this circumstance.
|||It makes me so frustrated!! I like to keep up to date, plus my old dev machine is getting on in years, so I splash out on a new PC with Vista, only to find I can't install SQL 2000 and am forced to use SQL 2005. I set everything up, make some changes to the database for my web app, then find I can't update the database on my web host's server because they're still on SQL 2000! I have no alternative but to run SQL 2000 on the old PC.
People ready!! my arse!
Restore 2005 to 2000 Database
The machine I do development on has SQL Server 2005 installed.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
My client, however, is running SQL Server 2000.
When I tried to restore the database, I got the error:
The backed-up database has on-disk structure version 611.
The server supports version 539 and cannot restore or upgrade the database.
How can I restore a SQL Server 2005 database to a SQL Server 2000 database?
You can not restore or attach a sql2005 db to sql2000.
You would need to export all the data, then import it back.|||That's pretty inconvenient!
Thanks for you help.
|||Ugh, that's awful. Way to make our lives hard, microsoft!
|||
At least the opposit is working!
So take a SQL Server 7, 2000 backup and restore it to a SQL Server 2005 Server. That is not true for master, model, msdb, but user database should work fine.
For doing the restore one has to use the option MOVE
|||I successfully attached a SQL 2005 database back into SQL 2000. However, that SQL 2005 database was originally from SQL 2000 and its compatibility was set to 80.
|||It's very interesting. Have you occured this error?:
Error 602: Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
We tried to attach our database back to SQL 2000, but this error occured.
|||The datadictonairy has changed completely. I think you should export all application tables in SQL Server 2000 and import them in SQL Server 2000. Be aware of the relationships :-)|||I'll say. That just happened to me also. the database grew from 32gigs to 72gigs since we installed 2005. We only need 2000 to migrate our data to a new version of the software we are using. Test it on 2005 in a test databse for a couple of weeks, then do it all over again for production database. errrrrr..|||You're asking to restore a much newer version of a database backup into an older versiion of the product. How can you possible expect this to work?
Would you expect Windows XP to run on an XT (Intel 8086) system? Of course not! So why expect the same here?
Your best option is to export the data.
Besides, who in their right mind develops something on a system that does not replicate their customers environment? Sounds like you haven't been in the game for long.
|||hi there
i'm facing the same problem...
1] I had SQL 2000 database dbTest...
2] attached that dbTest.mdf to sql 2005
3] now when trying to attach that same .mdf to sql 2000, i'm getting following error --
Error 602: Could not find row in sysindexes for database ID 9, object ID 1,
index ID 1. Run DBCC CHECKTABLE on sysindexes.
Can u please tell me how did u get ur error solved? Its a bit urgent...
Thanks in Advance!!
|||it is possible when you export the data from sql2005 then import to SQL 2000. An alternative method for this is to create 2 named instances within same computer. 1 for SQL 2005 and 1 for SQL 2000 on the same server.
Then export DB from SQL2005 to SQL2000. Afterwards backup your database in SQL2000.
It worked for me.. Yes i agree its a kind of catching the ear by a long way. But its better than it's not working.
I am not sure if Microsoft has announced backward compability of SQL 2005 Db's or supplied a detailed "How to" instruction or not; but they should have "SHOUT IT OUT LOUD" else this brings people anger when Microsoft emancipates itself like "We dont have to supply this compability"
So that; i'm in anger...
|||My view on this is that exporting from 2005 to 2000 is pretty easy using the export feature in 2005.
While I don't disagree with the view that you should develop on the same technology as your clients, I think most developers see SQL/Server as a collection of tables, views, indexes, relationships, i.e. not particulary using new features from SQL/Server 2005, so its pretty inconvenient not knowing how to do this, and for mixed client environments where some databases are 2005, others 2000, its essential.
Selecting export in 2005 and choosing all the objects, for me worked ok. If I had used a new feature in 2005 then fair enough, but I would not be wanting to export back to 2000 in this circumstance.
|||It makes me so frustrated!! I like to keep up to date, plus my old dev machine is getting on in years, so I splash out on a new PC with Vista, only to find I can't install SQL 2000 and am forced to use SQL 2005. I set everything up, make some changes to the database for my web app, then find I can't update the database on my web host's server because they're still on SQL 2000! I have no alternative but to run SQL 2000 on the old PC.
People ready!! my arse!
Subscribe to:
Posts (Atom)