Saturday, February 25, 2012

Restore a database with 2 datafiles into one datafile - possible?

Hi,
I do have a large Axapta database (114GB) with following file conent:
Datafiles:
d:\...\data\Axapta_data01.mdf - it is 87GB - it is in PRIMARY
Filegroup
f:\....\data\Axapta_data02.mdf - it is 27GB - also in PRIMARY
Filegroup
Logfile:
e:\...\log\Axapta_log02.ldf - 20 GB - none file group since it's
transactionlog file
Unfortunately does this application perform not well with this file
config (known problem within the Axapta enviroment)
So my issue is now following:
How can I move this database to a new server, and create only one
datafile?
I would like this new file config:
d:\....\data\Axapta_data01.mdf - 114GB - Primary filegroup
e:\....\log\axapta_log.ldf
Can anyone explain to me if it is possible, and then... how?
Thanks in advance...
Regards
TorgeirA restored database is exactly like the original so you can't change the
file configuration during the restore. If your plan is to move the database
using BACKP/RESTORE, you'll need to change the file configuration before the
backup or after the restore. To do this, expand the data01 file to the
desired size and then migrate data from data02 using DBCC
SHRINKFILE...EMPTYFILE. You can then remove the data02 file using ALTER
DATABASE.
Although it is not enforced, the file extension for secondary data files
should be 'ndf' rather than 'mdf'. The 'mdf' extension should be used only
for the primary data file in order to avoid later confusion.
--
Happy Holidays
Dan Guzman
SQL Server MVP
<dolerud@.start.no> wrote in message
news:1135896641.887437.220980@.g44g2000cwa.googlegroups.com...
> Hi,
> I do have a large Axapta database (114GB) with following file conent:
> Datafiles:
> d:\...\data\Axapta_data01.mdf - it is 87GB - it is in PRIMARY
> Filegroup
> f:\....\data\Axapta_data02.mdf - it is 27GB - also in PRIMARY
> Filegroup
> Logfile:
> e:\...\log\Axapta_log02.ldf - 20 GB - none file group since it's
> transactionlog file
> Unfortunately does this application perform not well with this file
> config (known problem within the Axapta enviroment)
> So my issue is now following:
> How can I move this database to a new server, and create only one
> datafile?
> I would like this new file config:
> d:\....\data\Axapta_data01.mdf - 114GB - Primary filegroup
> e:\....\log\axapta_log.ldf
> Can anyone explain to me if it is possible, and then... how?
> Thanks in advance...
> Regards
> Torgeir
>|||Hi, and thank you for your quick response!
I assume I also can do this operation after I have moved the database
to a new server.
The existing server do not have enought diskspace.
Regards
Torgeir|||Yes, you can consolidate the files after moving to the new server.
--
Happy Holidays
Dan Guzman
SQL Server MVP
<dolerud@.start.no> wrote in message
news:1135898358.019743.33740@.f14g2000cwb.googlegroups.com...
> Hi, and thank you for your quick response!
> I assume I also can do this operation after I have moved the database
> to a new server.
> The existing server do not have enought diskspace.
> Regards
> Torgeir
>

Restore a database with 2 datafiles into one datafile - possible?

Hi,
I do have a large Axapta database (114GB) with following file conent:
Datafiles:
d:\...\data\Axapta_data01.mdf - it is 87GB - it is in PRIMARY
Filegroup
f:\....\data\Axapta_data02.mdf - it is 27GB - also in PRIMARY
Filegroup
Logfile:
e:\...\log\Axapta_log02.ldf - 20 GB - none file group since it's
transactionlog file
Unfortunately does this application perform not well with this file
config (known problem within the Axapta enviroment)
So my issue is now following:
How can I move this database to a new server, and create only one
datafile?
I would like this new file config:
d:\....\data\Axapta_data01.mdf - 114GB - Primary filegroup
e:\....\log\axapta_log.ldf
Can anyone explain to me if it is possible, and then... how?
Thanks in advance...
Regards
TorgeirA restored database is exactly like the original so you can't change the
file configuration during the restore. If your plan is to move the database
using BACKP/RESTORE, you'll need to change the file configuration before the
backup or after the restore. To do this, expand the data01 file to the
desired size and then migrate data from data02 using DBCC
SHRINKFILE...EMPTYFILE. You can then remove the data02 file using ALTER
DATABASE.
Although it is not enforced, the file extension for secondary data files
should be 'ndf' rather than 'mdf'. The 'mdf' extension should be used only
for the primary data file in order to avoid later confusion.
Happy Holidays
Dan Guzman
SQL Server MVP
<dolerud@.start.no> wrote in message
news:1135896641.887437.220980@.g44g2000cwa.googlegroups.com...
> Hi,
> I do have a large Axapta database (114GB) with following file conent:
> Datafiles:
> d:\...\data\Axapta_data01.mdf - it is 87GB - it is in PRIMARY
> Filegroup
> f:\....\data\Axapta_data02.mdf - it is 27GB - also in PRIMARY
> Filegroup
> Logfile:
> e:\...\log\Axapta_log02.ldf - 20 GB - none file group since it's
> transactionlog file
> Unfortunately does this application perform not well with this file
> config (known problem within the Axapta enviroment)
> So my issue is now following:
> How can I move this database to a new server, and create only one
> datafile?
> I would like this new file config:
> d:\....\data\Axapta_data01.mdf - 114GB - Primary filegroup
> e:\....\log\axapta_log.ldf
> Can anyone explain to me if it is possible, and then... how?
> Thanks in advance...
> Regards
> Torgeir
>|||Hi, and thank you for your quick response!
I assume I also can do this operation after I have moved the database
to a new server.
The existing server do not have enought diskspace.
Regards
Torgeir|||Yes, you can consolidate the files after moving to the new server.
Happy Holidays
Dan Guzman
SQL Server MVP
<dolerud@.start.no> wrote in message
news:1135898358.019743.33740@.f14g2000cwb.googlegroups.com...
> Hi, and thank you for your quick response!
> I assume I also can do this operation after I have moved the database
> to a new server.
> The existing server do not have enought diskspace.
> Regards
> Torgeir
>

Restore a database to point in time?

Hello All,
Id like to restore a database to point in time in another SQL Server. I hav
e
a database backup from Production.
I created a new database in Development SQL Server. How can I restore a
database to point in time?
Were on SQL Server 2000.
Thanks in advance,
Do.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200507/1http://msdn.microsoft.com/library/d...>
kpc_6pv6.asp
David Portas
SQL Server MVP
--|||Hi,
The POINT-IN-TIME recovery will work only if the source database's Recovery
model is set to "FULL" and you should
have a full database backup + subsequent transaction log backups.
Steps:
1. Perform a transaction log backup of the original database (If you have
not performed one)
2. RESTORE DATABASE TEST1 FROM BBA (Give the correct backup file / device
name) WITH NORECOVERY
3. Restore the subsequent transaction log files in order of backup WITH
NORECOVERY option till the final transaction log file
4. In the the final transaction log restore mention WITH RECOVERY and
STOPAT='date and time'
Thanks
Hari
SQL Server MVP
"Do Park via droptable.com" <forum@.droptable.com> wrote in message
news:519E7397BD1DE@.droptable.com...
> Hello All,
> I'd like to restore a database to point in time in another SQL Server. I
> have
> a database backup from Production.
> I created a new database in Development SQL Server. How can I restore a
> database to point in time?
> We're on SQL Server 2000.
> Thanks in advance,
> Do.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200507/1

Restore a database to point in time?

Hello All,
Id like to restore a database to point in time in another SQL Server. I have
a database backup from Production.
I created a new database in Development SQL Server. How can I restore a
database to point in time?
Were on SQL Server 2000.
Thanks in advance,
Do.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200507/1
http://msdn.microsoft.com/library/de...ackpc_6pv6.asp
David Portas
SQL Server MVP
|||Hi,
The POINT-IN-TIME recovery will work only if the source database's Recovery
model is set to "FULL" and you should
have a full database backup + subsequent transaction log backups.
Steps:
1. Perform a transaction log backup of the original database (If you have
not performed one)
2. RESTORE DATABASE TEST1 FROM BBA (Give the correct backup file / device
name) WITH NORECOVERY
3. Restore the subsequent transaction log files in order of backup WITH
NORECOVERY option till the final transaction log file
4. In the the final transaction log restore mention WITH RECOVERY and
STOPAT='date and time'
Thanks
Hari
SQL Server MVP
"Do Park via droptable.com" <forum@.droptable.com> wrote in message
news:519E7397BD1DE@.droptable.com...
> Hello All,
> I'd like to restore a database to point in time in another SQL Server. I
> have
> a database backup from Production.
> I created a new database in Development SQL Server. How can I restore a
> database to point in time?
> We're on SQL Server 2000.
> Thanks in advance,
> Do.
>
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200507/1

Restore a database to point in time?

Hello All,
I?d like to restore a database to point in time in another SQL Server. I have
a database backup from Production.
I created a new database in Development SQL Server. How can I restore a
database to point in time?
We?re on SQL Server 2000.
Thanks in advance,
Do.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200507/1http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_7_backpc_6pv6.asp
--
David Portas
SQL Server MVP
--|||Hi,
The POINT-IN-TIME recovery will work only if the source database's Recovery
model is set to "FULL" and you should
have a full database backup + subsequent transaction log backups.
Steps:
1. Perform a transaction log backup of the original database (If you have
not performed one)
2. RESTORE DATABASE TEST1 FROM BBA (Give the correct backup file / device
name) WITH NORECOVERY
3. Restore the subsequent transaction log files in order of backup WITH
NORECOVERY option till the final transaction log file
4. In the the final transaction log restore mention WITH RECOVERY and
STOPAT='date and time'
Thanks
Hari
SQL Server MVP
"Do Park via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:519E7397BD1DE@.SQLMonster.com...
> Hello All,
> I'd like to restore a database to point in time in another SQL Server. I
> have
> a database backup from Production.
> I created a new database in Development SQL Server. How can I restore a
> database to point in time?
> We're on SQL Server 2000.
> Thanks in advance,
> Do.
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200507/1

restore a database to point in time

Should I need to restore a database to a specific point in
time, assuming full recovery model, are these steps
correct?
1. Back up Transactin Log
2. Restore Last Full backup and any differential backups
before the desired time.
3. Restore Transaction Log to specific point in time.
I am under the assumption that only tranasaction log
backups can be restored to a specific point in time, not
database backups, is this correct?Dan
You are correct that only transaction logs can restore to
a point in time.
If you are using differential backups, you only need to
restore the most recent one.
Your plan should work fine.
Regards
John|||Yes, you can only do point-in-time with transaction log restores.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"Dan" <anonymous@.discussions.microsoft.com> wrote in message
news:0d6d01c39e35$08002b70$a501280a@.phx.gbl...
Should I need to restore a database to a specific point in
time, assuming full recovery model, are these steps
correct?
1. Back up Transactin Log
2. Restore Last Full backup and any differential backups
before the desired time.
3. Restore Transaction Log to specific point in time.
I am under the assumption that only tranasaction log
backups can be restored to a specific point in time, not
database backups, is this correct?

Restore a database to another server

Hi, i am using sql server 2000, and i make daily backups. I want to
restore my backup to a test msde database i have. I don't know how i
did it last time.

-The database name is the same: "web" on both places
-The database is located on different hard drives and the file name
are different on both places.

I tried to do it from enterprise manager, restore database, from
device, i chose the transaction file and the database backup itself
and tried to restore, but i got an error that i don't have exclusive
access to the database.

How can i fix this?Seguros Catatumbo (seguroscatatumbo@.gmail.com) writes:

Quote:

Originally Posted by

Hi, i am using sql server 2000, and i make daily backups. I want to
restore my backup to a test msde database i have. I don't know how i
did it last time.
>
-The database name is the same: "web" on both places
-The database is located on different hard drives and the file name
are different on both places.
>
I tried to do it from enterprise manager, restore database, from
device, i chose the transaction file and the database backup itself
and tried to restore, but i got an error that i don't have exclusive
access to the database.


RESTORE DATABASE db FROM DISK ='filenamehere'
WITH MOVE 'logicalname1' TO 'path.mdf',
MOVE 'logicalname2' TO 'path_log.ldf',
REPLACE

logicalname1/2 are the logical names of the device file. You find these
with help of sp_helpdb on the source database, or RESTORE FILELISTONLY
on the backup file.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||

Quote:

Originally Posted by

RESTORE DATABASE db FROM DISK ='filenamehere'
WITH MOVE 'logicalname1' TO 'path.mdf',
MOVE 'logicalname2' TO 'path_log.ldf',
REPLACE
>


Hey Erland, thanks for replying. I couldn't get it to work. Here's the
command:

RESTORE DATABASE db FROM DISK ='c:\publica\web_db_200711150500.bak'
WITH MOVE 'WEB_Data' TO 'c:\pruebadb\web_dos.mdf',
MOVE 'WEB_Log' TO 'c:\pruebadb\web_dos_log.ldf',
REPLACE

Here's the error message:

The file 'c:\pruebadb\web_dos.mdf' cannot be overwritten. It is being
used by database 'web'.
File 'WEB_Data' cannot be restored to 'c:\pruebadb\web_dos.mdf'. Use
WITH MOVE to identify a valid location for the file.
The file 'c:\pruebadb\web_dos_log.ldf' cannot be overwritten. It is
being used by database 'web'.
File 'WEB_Log' cannot be restored to 'c:\pruebadb\web_dos_log.ldf'.
Use WITH MOVE to identify a valid location for the file.
RESTORE DATABASE is terminating abnormally.

Here's the output of sp_helpdb on the source db and destination db:

source:

WEB_Data
1D:\DataWEB\Data
\web_Data.MDF
PRIMARY4348096 KBUnlimited5120 KBdata only
WEB_Log
2D:\DataWEB\Data
\web_Log.LDF
NULL32448 KBUnlimited10%log only

destination:

WEB_Data
1C:\pruebadb
\web_dos.mdf
PRIMARY2092928 KBUnlimited5120 KBdata only
WEB_Log
2C:\pruebadb
\web_dos_log.ldf
NULL1024 KBUnlimited10%log only

The c:\publica\web_db_200711150500.bak was obtained from a backup made
by sql server itself on the source server itself|||I made a mistake with the command. My database name is not db, it's
"web". So now i get the same error i get when i do with the GUI:

RESTORE DATABASE db FROM DISK ='c:\publica\web_db_200711150500.bak'
WITH MOVE 'WEB_Data' TO 'c:\pruebadb\web_dos.mdf',
MOVE 'WEB_Log' TO 'c:\pruebadb\web_dos_log.ldf',
REPLACE

Here's the error message:

Exclusive access could not be obtained because the database is in use.

Do i need to take the database offline or something?|||Ok, i think i know how to fix it.

-WEB is my default database, so when i use query analizer it opens
that database. It can't restore the database if i am connected. So
instead of figuring off how to change the default database, i
connected, changed the current db to master (use master), and then i
could take web offline with enterprise manager. Now the command seems
to be working, it will take long, the database is 4GB.

RESTORE DATABASE web FROM DISK ='c:\publica\web_db_200711150500.bak'
WITH MOVE 'WEB_Data' TO 'c:\pruebadb\web_dos.mdf',
MOVE 'WEB_Log' TO 'c:\pruebadb\web_dos_log.ldf',
REPLACE|||Yup, it worked, so the conclusion is that it would have worked from
the start if i just would have taken the database offline. Thanks for
your help

restore a database on MSDE

Hi,
I habe a MSDE 2000 on a server machine. I don't habe "Enterprise Manager" or
"SQL Analyzer".
How can I restore a backup database?
This machine had MS Access XP, I can write program with VB6. Is there anyway
to execute a SQL script "RESTORE DATABASE ..."?
Thanks for help
Martin
Hi
Have a look at:
http://groups.google.ch/group/micros...346b3cfb2904bb
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Martin" <martinsm@.freenet.de> wrote in message
news:ON%23oAxn0FHA.164@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I habe a MSDE 2000 on a server machine. I don't habe "Enterprise Manager"
> or
> "SQL Analyzer".
> How can I restore a backup database?
> This machine had MS Access XP, I can write program with VB6. Is there
> anyway
> to execute a SQL script "RESTORE DATABASE ..."?
> Thanks for help
> Martin
>
>
|||Look at http://www.asql.biz/DbaMgr.shtmn it's an graphical interface.

Restore a database on clustered server from a non-clustered backup file.

Hello,

How do I restore a sql database that is on a clustered server from a sql database backup file that is on a non_clustered server?

Thanks,

Serey

Just like how you do it if it is not clustered. Clustering is transparent to SQL Server.|||There is no difference between clustered and non clustered servers in terms of how you restore a backup. Will work the same way.

Restore a database from Yukon to SQL 2000 SP4 edition?

Hello,
I have a siuation that need restore a testing database that currently running on Yukon server to SQL 2000 SP4 staging server. I am getting an error when I go with filelistonly option to see if its possible.
### Error Starts ###
Server: Msg 3169, Level 16, State 1, Line 1
The backed-up database has on-disk structure version 603. The server supports version 539 and cannot restore or upgrade this database.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE FILELIST is terminating abnormally.
### Error Ends ###

Yes, I am trying to downgrade it, any way that I can do?

Thanks in advance.

Sunny Jung

Sunny,

There is no way to downgrade. You can try to export the data and them import it. But this isn't a scenario we test.

Dan

Restore a database from SQL Server 2000 to SQL Server 2005 Express

Hi,
I'm trying to restore a database that existed in SQL Server 2000 to SQL
Server 2005 Express edition and I keep getting the following error:
System.Data.SqlClient.SqlError: Directory lookup for the file (name of the
file) failed with the operating system error 5(Access is denied.).
(Microsoft.SqlServer.Express.Smo)
I backed up the database using SQL Server 2000 and I simply want to restore
the database in 2005 Express.
The system is XP Professional and I am logged on as the administrator.
I'm using SQL Server and Windows Authentication mode in both SQL Server 2000
and in SQL Server 2005 Express.
Any ideas.
Thanks,
--
Scott H.Scott
Any errors in Event Viewer, SQL Server LOG file?
"Scott H." <ScottH@.discussions.microsoft.com> wrote in message
news:FD12F53E-3D00-4733-8FAD-42C4D790C03B@.microsoft.com...
> Hi,
> I'm trying to restore a database that existed in SQL Server 2000 to SQL
> Server 2005 Express edition and I keep getting the following error:
> System.Data.SqlClient.SqlError: Directory lookup for the file (name of the
> file) failed with the operating system error 5(Access is denied.).
> (Microsoft.SqlServer.Express.Smo)
> I backed up the database using SQL Server 2000 and I simply want to
> restore
> the database in 2005 Express.
> The system is XP Professional and I am logged on as the administrator.
> I'm using SQL Server and Windows Authentication mode in both SQL Server
> 2000
> and in SQL Server 2005 Express.
> Any ideas.
> Thanks,
> --
> Scott H.

Restore a database

Hello

Please, help me

I need to know, how to restore the database (base.bak) on MS SQL Server 2005 Ex. Ed. from my WinForm Application

I programming on C#.

Please, if you can, give me a code on C#.

Thanks

Try the following info found at http://www.csharphelp.com/archives2/archive345.html

SQL Server Backup/Restore Through SQLDMO and C#

Restore a database

Hello

Please, help me

I need to know, how to restore the database (base.bak) on MS SQL Server 2005 Ex. Ed. from my WinForm Application

I programming on C#.

Please, if you can, give me a code on C#.

Thanks

Try the following info found at http://www.csharphelp.com/archives2/archive345.html

SQL Server Backup/Restore Through SQLDMO and C#

Restore a database

hello,

How to restore a database without the master database?

Regards,

without the master database, your sql server instance will not be able to start up.

no, you do not need to restore the master database before restoring your user database.

restore a database

Hi,
I have a msde backup file.
I want restore a database with this backup file, but i get
the following error :"Error 3256
The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally"
I suspect that the .ldf file is damaged.
How i can manage this situation ?
Can I restore a database without a transaction log.
Others backups are not avalaible.
Could you help me?
Thanks

GianoTo attach the database you should have .MDF which should be properly detached earlier. Your query refers to backup file that means it may be .bak file or to a backup device.

And 3256 error indicates that the backup set is not complete because the backup operation that created the backup set did not finish successfully.

So make sure to take full backup without any interruption.

Restore a basebase on sql server 2000 sp4 from a backup from sql server 2000 sp3

Is this safe. or can it cause any problems.
The reson I ask is because I see the following error "[DBNetlinb]
connectioncheckfordata" when I execute (from query analyser or osql)
Insert Into temptable select ... from [databasesource].source ...
both databases running on the same server
I have an number of insert to temptable and only one of them fails. But if I
use a top it works.
Insert Into temptable select top 1000... from [databasesource].source ..
.
And another thing I have tested it before the upgrade from sp3 to sp4 and
everything work fine.
Any clue.
Thank
LasseServer
I have just restored a database from SP3 to SP4. Works fime for me.
"Server Applications" <NoSpam@.dk.dk> wrote in message
news:O5zPA3e5FHA.1464@.tk2msftngp13.phx.gbl...
> Is this safe. or can it cause any problems.
> The reson I ask is because I see the following error "[DBNetlinb]
> connectioncheckfordata" when I execute (from query analyser or osql)
> Insert Into temptable select ... from [databasesource].source ...
> both databases running on the same server
> I have an number of insert to temptable and only one of them fails. But if
> I
> use a top it works.
> Insert Into temptable select top 1000... from [databasesource].source
..
> And another thing I have tested it before the upgrade from sp3 to sp4 and
> everything work fine.
> Any clue.
> Thank
> Lasse
>

Restore a basebase on sql server 2000 sp4 from a backup from sql server 2000 sp3

Is this safe. or can it cause any problems.
The reson I ask is because I see the following error "[DBNetlinb]
connectioncheckfordata" when I execute (from query analyser or osql)
Insert Into temptable select ... from [databasesource].source ...
both databases running on the same server
I have an number of insert to temptable and only one of them fails. But if I
use a top it works.
Insert Into temptable select top 1000... from [databasesource].source ...
And another thing I have tested it before the upgrade from sp3 to sp4 and
everything work fine.
Any clue.
Thank
Lasse
Server
I have just restored a database from SP3 to SP4. Works fime for me.
"Server Applications" <NoSpam@.dk.dk> wrote in message
news:O5zPA3e5FHA.1464@.tk2msftngp13.phx.gbl...
> Is this safe. or can it cause any problems.
> The reson I ask is because I see the following error "[DBNetlinb]
> connectioncheckfordata" when I execute (from query analyser or osql)
> Insert Into temptable select ... from [databasesource].source ...
> both databases running on the same server
> I have an number of insert to temptable and only one of them fails. But if
> I
> use a top it works.
> Insert Into temptable select top 1000... from [databasesource].source ...
> And another thing I have tested it before the upgrade from sp3 to sp4 and
> everything work fine.
> Any clue.
> Thank
> Lasse
>

Restore a basebase on sql server 2000 sp4 from a backup from sql server 2000 sp3

Is this safe. or can it cause any problems.
The reson I ask is because I see the following error "[DBNetlinb]
connectioncheckfordata" when I execute (from query analyser or osql)
Insert Into temptable select ... from [databasesource].source ...
both databases running on the same server
I have an number of insert to temptable and only one of them fails. But if I
use a top it works.
Insert Into temptable select top 1000... from [databasesource].source ...
And another thing I have tested it before the upgrade from sp3 to sp4 and
everything work fine.
Any clue.
Thank
LasseServer
I have just restored a database from SP3 to SP4. Works fime for me.
"Server Applications" <NoSpam@.dk.dk> wrote in message
news:O5zPA3e5FHA.1464@.tk2msftngp13.phx.gbl...
> Is this safe. or can it cause any problems.
> The reson I ask is because I see the following error "[DBNetlinb]
> connectioncheckfordata" when I execute (from query analyser or osql)
> Insert Into temptable select ... from [databasesource].source ...
> both databases running on the same server
> I have an number of insert to temptable and only one of them fails. But if
> I
> use a top it works.
> Insert Into temptable select top 1000... from [databasesource].source ...
> And another thing I have tested it before the upgrade from sp3 to sp4 and
> everything work fine.
> Any clue.
> Thank
> Lasse
>

restore a bakup database on MSDE

Hi,
I habe a MSDE 2000 on a server machine. I don't habe "Enterprise Manager" or
"SQL Analyzer".
How can I restore a backup database?
This machine had MS Access XP, I can write program with VB6. Is there anyway
to execute a SQL script "RESTORE DATABASE ..."?
Thanks for help
Martin
Hi,
You have 2 options:-
1. OSQL :- MSDE comes with command line utility OSQL. Using this you can
login to SQL Server and execute any TSQL command. For
Restore you can use RESTORE DATABASE command from OSQL.
2. Webadmin:- Web based free tool from microsoft. Download from below site:-
http://www.microsoft.com/downloads/d...displaylang=en
Thanks
Hari
SQL Server MVP
"Martin" <martinsm@.freenet.de> wrote in message
news:ulVz$wn0FHA.164@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I habe a MSDE 2000 on a server machine. I don't habe "Enterprise Manager"
> or
> "SQL Analyzer".
> How can I restore a backup database?
> This machine had MS Access XP, I can write program with VB6. Is there
> anyway
> to execute a SQL script "RESTORE DATABASE ..."?
> Thanks for help
> Martin
>
>
|||Option 3:
make a little program, logon to master database and execute restore database
statement
RESTORE DATABASE <dbname> FROM DISK <location> WITH MOVE <file name>, TO
<file name>, RECOVERY, REPLACE
(MOVE and TO twice, for ldf and mdf (more if ndf's))
Check out BOL for exact statement
Lee-Z
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23bq4c3s0FHA.1132@.TK2MSFTNGP10.phx.gbl...
> Hi,
> You have 2 options:-
> 1. OSQL :- MSDE comes with command line utility OSQL. Using this you can
> login to SQL Server and execute any TSQL command. For
> Restore you can use RESTORE DATABASE command from OSQL.
> 2. Webadmin:- Web based free tool from microsoft. Download from below
> site:-
> http://www.microsoft.com/downloads/d...displaylang=en
> Thanks
> Hari
> SQL Server MVP
>
> "Martin" <martinsm@.freenet.de> wrote in message
> news:ulVz$wn0FHA.164@.TK2MSFTNGP10.phx.gbl...
>
|||Thanks
"Hari Prasad" <hari_prasad_k@.hotmail.com> schrieb im Newsbeitrag
news:#bq4c3s0FHA.1132@.TK2MSFTNGP10.phx.gbl...
> Hi,
> You have 2 options:-
> 1. OSQL :- MSDE comes with command line utility OSQL. Using this you can
> login to SQL Server and execute any TSQL command. For
> Restore you can use RESTORE DATABASE command from OSQL.
> 2. Webadmin:- Web based free tool from microsoft. Download from below
site:-
>
http://www.microsoft.com/downloads/d...798-C57A-419E-
ACBC-2A332CB7F959&displaylang=en[vbcol=seagreen]
> Thanks
> Hari
> SQL Server MVP
>
> "Martin" <martinsm@.freenet.de> wrote in message
> news:ulVz$wn0FHA.164@.TK2MSFTNGP10.phx.gbl...
Manager"
>

Restore a backup to a different db name and path

I have the following situation:
Database1 on my sql server with the following path: C:\DBs
\Database1.mdf, etc... I made a backup of this database. Now I need
to restore this backup on a different pc into the following: Database2
with the following path C:\Customers\DBS\Database2.mdf, etc... I have
MSDE install on the pc so I dont have the enterprise manager that will
allow me to restore a db and rename the path and file name. What is
the script that I need to run using the osql command?
Thanks
Drop $35 bucks and get the Developer Edition. It has all the tools you need.
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest books:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and
Hitchhiker's Guide to SQL Server 2005 Compact Edition
------
"Monica" <Monica@.discussions.microsoft.com> wrote in message
news:42F8C3FE-6410-4083-A3EF-453895ABA12C@.microsoft.com...
>I have the following situation:
> Database1 on my sql server with the following path: C:\DBs
> \Database1.mdf, etc... I made a backup of this database. Now I need
> to restore this backup on a different pc into the following: Database2
> with the following path C:\Customers\DBS\Database2.mdf, etc... I have
> MSDE install on the pc so I dont have the enterprise manager that will
> allow me to restore a db and rename the path and file name. What is
> the script that I need to run using the osql command?
> Thanks
|||=?Utf-8?B?TW9uaWNh?= <Monica@.discussions.microsoft.com> wrote in
news:42F8C3FE-6410-4083-A3EF-453895ABA12C@.microsoft.com:

> I have the following situation:
> Database1 on my sql server with the following path: C:\DBs
> \Database1.mdf, etc... I made a backup of this database. Now I need
> to restore this backup on a different pc into the following: Database2
> with the following path C:\Customers\DBS\Database2.mdf, etc... I have
> MSDE install on the pc so I dont have the enterprise manager that will
> allow me to restore a db and rename the path and file name. What is
> the script that I need to run using the osql command?
> Thanks
something like
RESTORE DATABASE [Database2]
FROM DISK='full_path_of_backup_file'
WITH MOVE 'Database1' TO 'C:\Customers\DBS\Database2.mdf',
MOVE 'Database1_log' TO 'C:\Customers\DBS\Database2_log.ldf'
See BOL for the gory details
|||Thanks...
I tried that but now I get this:
Server: Msg 3234, Level 16, State 2, Line 1
Logical file 'Database1' is not part of database 'Database2'. Use RESTORE
FILELISTONLY to list the logical file names.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
|||=?Utf-8?B?TW9uaWNh?= <Monica@.discussions.microsoft.com> wrote in
news:6C6F4DE3-3AE6-4753-AB7D-4CB063CDA122@.microsoft.com:

> Thanks...
> I tried that but now I get this:
> Server: Msg 3234, Level 16, State 2, Line 1
> Logical file 'Database1' is not part of database 'Database2'. Use
> RESTORE FILELISTONLY to list the logical file names.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
Sorry, it would appear that the 'logical name' of your database is NOT
Database1. To find what the logical name is, do what the message says by
running the query
RESTORE FILELISTONLY
FROM DISK='full_path_of_backup_file'
Then, in what I wrote before
RESTORE DATABASE [Database2]
FROM DISK='full_path_of_backup_file'
WITH MOVE 'Database1' TO 'C:\Customers\DBS\Database2.mdf',
MOVE 'Database1_log' TO 'C:\Customers\DBS\Database2_log.ldf'
change MOVE 'Database1' to be MOVE 'logicalname1' and
MOVE 'Database1_log' to be MOVE 'logicalname2' (probably MOVE
'logicalname1_log') for whatever logicalnames are shown by RESTORE
FILELISTONLY
FWIW I have just run the following renaming-restore successfully for
myself
RESTORE DATABASE [Database2]
FROM DISK='C:\Documents and Settings\chris\My Documents\Databases
\Cambridge-41a-Backup-2005-06-03'
WITH MOVE 'Cambridge-41' TO 'C:\Documents and Settings\chris\My
Documents\Databases\Database2.mdf',
MOVE 'Cambridge-41_log' TO 'C:\Documents and Settings\chris\My
Documents\Databases\Database2_log.ldf'
(cut-and-pasted) so it's just a matter of making the appropriate changes
(making sure that the commas, quotes, etc are in the correct places).
HTH

Restore a backup to a database using SQLDMO

Hai...
I am working on VC++. I need to restore the backup to the
database(SQL SERVER) using SQLDMO in VC++. I am able to restore the
backup only to the database where i taken the backup but to some other
database it fails. Can anyone provide me the solution for restoring the
backup to some other database? Looking for the reply...
Thanx in advance...
Regards,
PrinceYou need to set the Backup object ReplaceDatabase property to TRUE. From
the Books Online:
<Excerpt href="http://links.10026.com/?link=sqldmo.chm::/dmoref_p_r_1cop.htm">
If TRUE, a new image of the database is created. The image is created
regardless of the presence of an existing database with the same name.
If FALSE (default), a new image of the database is not created by the
restore operation. The database targeted by the restore operation must exist
on an instance of Microsoft SQL ServerT 2000.
</Excerpt>
Hope this helps.
Dan Guzman
SQL Server MVP
"Prince" <princevictor.moses@.gmail.com> wrote in message
news:1124188828.330558.78130@.z14g2000cwz.googlegroups.com...
> Hai...
> I am working on VC++. I need to restore the backup to the
> database(SQL SERVER) using SQLDMO in VC++. I am able to restore the
> backup only to the database where i taken the backup but to some other
> database it fails. Can anyone provide me the solution for restoring the
> backup to some other database? Looking for the reply...
> Thanx in advance...
> Regards,
> Prince
>

Restore a backup from SQL 2005 to SQL 2000

Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?
Zack wrote:
> Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?
>
Nope. This has been asked here about six times in the past 2 weeks,
search around and you'll find some alternative suggestions.
Backup/restore is not possible.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Hi,
Due to architectual differences you can not restore a database backup from
higher version to Lower version [SQL 2005 to SQL 2000] . But it is always
possible to restore the
SQL Server 2000 backup to SQL Server 2005 server. Only solution is to create
the database manually, create objects and use SSIS/DTS/BCP to transfer the
data.
Thanks
Hari
"Zack" <svoiasgfs@.sdlgweg90dflg.com> wrote in message
news:eTRxDDCCHHA.4672@.TK2MSFTNGP02.phx.gbl...
> Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?
>

Restore a backup from SQL 2005 to SQL 2000

Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?Zack wrote:
> Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?
>
Nope. This has been asked here about six times in the past 2 weeks,
search around and you'll find some alternative suggestions.
Backup/restore is not possible.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi,
Due to architectual differences you can not restore a database backup from
higher version to Lower version [SQL 2005 to SQL 2000] . But it is always
possible to restore the
SQL Server 2000 backup to SQL Server 2005 server. Only solution is to create
the database manually, create objects and use SSIS/DTS/BCP to transfer the
data.
Thanks
Hari
"Zack" <svoiasgfs@.sdlgweg90dflg.com> wrote in message
news:eTRxDDCCHHA.4672@.TK2MSFTNGP02.phx.gbl...
> Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?
>

Restore a backup from SQL 2005 to SQL 2000

Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?Zack wrote:
> Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?
>
Nope. This has been asked here about six times in the past 2 weeks,
search around and you'll find some alternative suggestions.
Backup/restore is not possible.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi,
Due to architectual differences you can not restore a database backup from
higher version to Lower version [SQL 2005 to SQL 2000] . But it is alway
s
possible to restore the
SQL Server 2000 backup to SQL Server 2005 server. Only solution is to create
the database manually, create objects and use SSIS/DTS/BCP to transfer the
data.
Thanks
Hari
"Zack" <svoiasgfs@.sdlgweg90dflg.com> wrote in message
news:eTRxDDCCHHA.4672@.TK2MSFTNGP02.phx.gbl...
> Is it possible to restore a backup from SQL 2005 to a SQL 2000 server?
>

restore a backup db on MSDE

Hi,
I habe a MSDE 2000 on a server machine. I don't habe "Enterprise Manager" or
"SQL Analyzer".
How can I restore a backup database?
This machine had MS Access XP, I can write program with VB6. Is there anyway
to execute a SQL script "RESTORE DATABASE ..."?
Thanks for help
Martin
Yes, you can use OSQL.EXE and from there execute your RESTORE command. Both OSQL and RESTORE are
documented in Books Online, which you can find here:
http://www.microsoft.com/sql/techinf...0/default.mspx
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Martin" <martinsm@.freenet.de> wrote in message news:uE7SAxn0FHA.164@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I habe a MSDE 2000 on a server machine. I don't habe "Enterprise Manager" or
> "SQL Analyzer".
> How can I restore a backup database?
> This machine had MS Access XP, I can write program with VB6. Is there anyway
> to execute a SQL script "RESTORE DATABASE ..."?
> Thanks for help
> Martin
>
>
|||Am Sun, 16 Oct 2005 15:36:34 +0200 schrieb Martin:

> Hi,
> I habe a MSDE 2000 on a server machine. I don't habe "Enterprise Manager" or
> "SQL Analyzer".
> How can I restore a backup database?
> This machine had MS Access XP, I can write program with VB6. Is there anyway
> to execute a SQL script "RESTORE DATABASE ..."?
> Thanks for help
> Martin
You can use DbaMgr2k from http://www.asql.biz/DbaMgr.shtm
A free and mighty Admin-Tool for SQL-Server and MSDE, can backup and
restore too.
bye,
Helmut

Restore 8-CPU master to 4-CPU server. What will happen?

Hi,
Restore 8-CPU master to 4-CPU server. What will happen? Can this be done at
all?
(MS SQL Server 2000 SP3 to SQL Server 2000 SP3 , Windows Server 2003 SP1 to
Windows Server 2000 SP4).
-- Many thanks, Oskar.Number of processors doesn't matter. (though I'm not sure about the exact
behavior if you have set processor affinity, never tried it).
Linchi
"Oskar" wrote:

> Hi,
> Restore 8-CPU master to 4-CPU server. What will happen? Can this be done a
t
> all?
> (MS SQL Server 2000 SP3 to SQL Server 2000 SP3 , Windows Server 2003 SP1 t
o
> Windows Server 2000 SP4).
> -- Many thanks, Oskar.
>

Restore 8-CPU master to 4-CPU server. What will happen?

Hi,
Restore 8-CPU master to 4-CPU server. What will happen? Can this be done at
all?
(MS SQL Server 2000 SP3 to SQL Server 2000 SP3 , Windows Server 2003 SP1 to
Windows Server 2000 SP4).
-- Many thanks, Oskar.
Number of processors doesn't matter. (though I'm not sure about the exact
behavior if you have set processor affinity, never tried it).
Linchi
"Oskar" wrote:

> Hi,
> Restore 8-CPU master to 4-CPU server. What will happen? Can this be done at
> all?
> (MS SQL Server 2000 SP3 to SQL Server 2000 SP3 , Windows Server 2003 SP1 to
> Windows Server 2000 SP4).
> -- Many thanks, Oskar.
>

RESTORE 64-bit database via 32-bit GUI...

Hello all,
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...
Hi
On the 32 bit client, have you installed a minimum of sp3a?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:8C8842C1-37B4-4AFB-BCB4-A63FD58DC323@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>
|||Yeah, it's 8.00.760 (SP3)...
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> On the 32 bit client, have you installed a minimum of sp3a?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
> news:8C8842C1-37B4-4AFB-BCB4-A63FD58DC323@.microsoft.com...
>
>

RESTORE 64-bit database via 32-bit GUI...

Hello all,
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...Hi
On the 32 bit client, have you installed a minimum of sp3a?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:8C8842C1-37B4-4AFB-BCB4-A63FD58DC323@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>|||Yeah, it's 8.00.760 (SP3)...
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> On the 32 bit client, have you installed a minimum of sp3a?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
> news:8C8842C1-37B4-4AFB-BCB4-A63FD58DC323@.microsoft.com...
> > Hello all,
> >
> > I'm trying to use the 32-bit GUI, on a remote server, to restore a
> > database
> > on one of our 64-bit servers. The GUI returns a prompt that the restore
> > was
> > successful but the GUI indicates that the database is in a Loading mode.
> > I
> > tried to issue a recovery command but it fails saying that some of the
> > files
> > were partially restored.
> >
> > I figured that there is a problem using the 32-bit client utility so I
> > used
> > OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> > compatible 64-bit utility. By doing so, I was able to restore the
> > database
> > successfully.
> >
> > So my question is, is not being able to restore a 64-bit database via a
> > 32-bit GUI, on a remote server, a known issue?
> >
> > Thanks...
> >
>
>

RESTORE 64-bit database via 32-bit GUI...

Hello all,
I'm trying to use the 32-bit GUI, on a remote server, to restore a database
on one of our 64-bit servers. The GUI returns a prompt that the restore was
successful but the GUI indicates that the database is in a Loading mode. I
tried to issue a recovery command but it fails saying that some of the files
were partially restored.
I figured that there is a problem using the 32-bit client utility so I used
OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
compatible 64-bit utility. By doing so, I was able to restore the database
successfully.
So my question is, is not being able to restore a 64-bit database via a
32-bit GUI, on a remote server, a known issue?
Thanks...Hi
On the 32 bit client, have you installed a minimum of sp3a?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:8C8842C1-37B4-4AFB-BCB4-A63FD58DC323@.microsoft.com...
> Hello all,
> I'm trying to use the 32-bit GUI, on a remote server, to restore a
> database
> on one of our 64-bit servers. The GUI returns a prompt that the restore
> was
> successful but the GUI indicates that the database is in a Loading mode.
> I
> tried to issue a recovery command but it fails saying that some of the
> files
> were partially restored.
> I figured that there is a problem using the 32-bit client utility so I
> used
> OSQL, via SQL Server Agent, on the 64-bit to ensure that I was using a
> compatible 64-bit utility. By doing so, I was able to restore the
> database
> successfully.
> So my question is, is not being able to restore a 64-bit database via a
> 32-bit GUI, on a remote server, a known issue?
> Thanks...
>|||Yeah, it's 8.00.760 (SP3)...
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> On the 32 bit client, have you installed a minimum of sp3a?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
> news:8C8842C1-37B4-4AFB-BCB4-A63FD58DC323@.microsoft.com...
>
>

restore 64 to 32 bit

Hi

We have a running SQL server 2005 (x64) and I want to do a restretest, but I do not have a 64 server.

Is it possible to do a restore to a 32 Bit server?

Regards

Kim

It isn′t possible because the binary files of 64 BIT is different of 32 BIT. I had a bad experience with this.|||

I do not agree with the previous post I'm afraid.

The file structure of the database is EXACTLY the same for 32-bit and 64-bit. This means you can use the file on either version of SQL Server 2005.

We have a daily backup from a SQL Server 2005 x64 database that gets distributed to several x64 and x86 servers.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

Yes it's possible. I've done it quite a few times without any problems. The backups, data and log files are not 64 bit. They are just SQL Server files.

-Sue

Restore 6.5 backup file to 7 or 2000

I have a Sql Server database backup file from version 6.5
that I need to restore to either 7 or 2000. Is there any
way to get this DAT file restored to a later version of
SQL?No, you must restore it to a 6.5 db first and then you can upgrade it from
there.
--
Andrew J. Kelly
SQL Server MVP
"T Craig" <tcraig@.cfl.rr.com> wrote in message
news:328e01c373f8$a7076830$a601280a@.phx.gbl...
> I have a Sql Server database backup file from version 6.5
> that I need to restore to either 7 or 2000. Is there any
> way to get this DAT file restored to a later version of
> SQL?

Restore 32bit/64bit

Hello,
I am completely SQL ignorant, so please be gentle!!!
Are SQL 2005 64 bit databases constructed differently to SQL 2005 32
bit databases? For example, could I restore/import a database created
in the 64 bit version to a 32 bit version of SQL 2005?
ThanksThere is no restriction in restoring backups made from a 32 bit or 64
bit instance of SQL Server to the opposite. The same is true for
DETACH and ATTACH. The databases are internally identical.
Roy Harvey
Beacon Falls, CT
On Tue, 29 Apr 2008 08:59:08 -0700 (PDT), tvmo <tvmo@.hotmail.co.uk>
wrote:
>Hello,
>I am completely SQL ignorant, so please be gentle!!!
>Are SQL 2005 64 bit databases constructed differently to SQL 2005 32
>bit databases? For example, could I restore/import a database created
>in the 64 bit version to a 32 bit version of SQL 2005?
>Thanks|||No problem. The two are compatible with each other.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"tvmo" <tvmo@.hotmail.co.uk> wrote in message
news:188289e5-d993-4294-94cd-d183a0c22ed7@.25g2000hsx.googlegroups.com...
Hello,
I am completely SQL ignorant, so please be gentle!!!
Are SQL 2005 64 bit databases constructed differently to SQL 2005 32
bit databases? For example, could I restore/import a database created
in the 64 bit version to a 32 bit version of SQL 2005?
Thanks|||Thanks very much both.
So the only difference is how the application interacts with the
hardware?
Cheers.|||If you by "Application" mean SQL Server, then yes. The application is 64 bit with 64 bit
instructions etc. To be more specific, though, we should say that the app interacts with the
operating system, which in turn interacts with the hardware.
Note that you should be careful if you go down-level in edition, since the database might use some
feature in a higher edition - which isn't available in the lower edition.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"tvmo" <tvmo@.hotmail.co.uk> wrote in message
news:faee31f3-c5dd-4c77-99c8-7c5e15f6cbf0@.f63g2000hsf.googlegroups.com...
> Thanks very much both.
> So the only difference is how the application interacts with the
> hardware?
> Cheers.|||Thanks very much all.

restore 2k backup on sql 7

can i restore sql 2k backup on sql 7?Hi,
No, you cant restore a SQL 2000 database backup to SQL 7 due to
architectural changes.
The otherway from SQL 7 to SQL 2000 is possible.
Thanks
Hari
MCDBA
"harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
> can i restore sql 2k backup on sql 7?
>|||Yeah I knew it just had to confirm.
THanks.
Can I connect to SQL server using sql 7 EM? currently it is not allowing me
to connect, but some one told me that there is a work around.
regards,
Harshal.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:uTB7Ym9OEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> No, you cant restore a SQL 2000 database backup to SQL 7 due to
> architectural changes.
> The otherway from SQL 7 to SQL 2000 is possible.
> Thanks
> Hari
> MCDBA
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
>|||Hi,
As far as i know there is no work around to connect SQL 2000 Server using
SQL 7 server EM.
Thanks
Hari
MCDBA
"harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:e1zLh39OEHA.736@.tk2msftngp13.phx.gbl...
> Yeah I knew it just had to confirm.
> THanks.
> Can I connect to SQL server using sql 7 EM? currently it is not allowing
me
> to connect, but some one told me that there is a work around.
> regards,
> Harshal.
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:uTB7Ym9OEHA.2716@.tk2msftngp13.phx.gbl...
>|||ok .
thanks for the help.
regards,
Harshal.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:eL44D6%23OEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> As far as i know there is no work around to connect SQL 2000 Server using
> SQL 7 server EM.
>
> Thanks
> Hari
> MCDBA
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:e1zLh39OEHA.736@.tk2msftngp13.phx.gbl...
> me
>

restore 2k backup on sql 7

can i restore sql 2k backup on sql 7?
Hi,
No, you cant restore a SQL 2000 database backup to SQL 7 due to
architectural changes.
The otherway from SQL 7 to SQL 2000 is possible.
Thanks
Hari
MCDBA
"harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
> can i restore sql 2k backup on sql 7?
>
|||Yeah I knew it just had to confirm.
THanks.
Can I connect to SQL server using sql 7 EM? currently it is not allowing me
to connect, but some one told me that there is a work around.
regards,
Harshal.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:uTB7Ym9OEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> No, you cant restore a SQL 2000 database backup to SQL 7 due to
> architectural changes.
> The otherway from SQL 7 to SQL 2000 is possible.
> Thanks
> Hari
> MCDBA
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
>
|||Hi,
As far as i know there is no work around to connect SQL 2000 Server using
SQL 7 server EM.
Thanks
Hari
MCDBA
"harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:e1zLh39OEHA.736@.tk2msftngp13.phx.gbl...
> Yeah I knew it just had to confirm.
> THanks.
> Can I connect to SQL server using sql 7 EM? currently it is not allowing
me
> to connect, but some one told me that there is a work around.
> regards,
> Harshal.
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:uTB7Ym9OEHA.2716@.tk2msftngp13.phx.gbl...
>
|||ok .
thanks for the help.
regards,
Harshal.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:eL44D6%23OEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> As far as i know there is no work around to connect SQL 2000 Server using
> SQL 7 server EM.
>
> Thanks
> Hari
> MCDBA
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:e1zLh39OEHA.736@.tk2msftngp13.phx.gbl...
> me
>

restore 2k backup on sql 7

can i restore sql 2k backup on sql 7?Hi,
No, you cant restore a SQL 2000 database backup to SQL 7 due to
architectural changes.
The otherway from SQL 7 to SQL 2000 is possible.
Thanks
Hari
MCDBA
"harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
> can i restore sql 2k backup on sql 7?
>|||Yeah I knew it just had to confirm.
THanks.
Can I connect to SQL server using sql 7 EM? currently it is not allowing me
to connect, but some one told me that there is a work around.
regards,
Harshal.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:uTB7Ym9OEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> No, you cant restore a SQL 2000 database backup to SQL 7 due to
> architectural changes.
> The otherway from SQL 7 to SQL 2000 is possible.
> Thanks
> Hari
> MCDBA
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
> > can i restore sql 2k backup on sql 7?
> >
> >
>|||Hi,
As far as i know there is no work around to connect SQL 2000 Server using
SQL 7 server EM.
Thanks
Hari
MCDBA
"harshal mistry" <harshal_in@.hotmail.com> wrote in message
news:e1zLh39OEHA.736@.tk2msftngp13.phx.gbl...
> Yeah I knew it just had to confirm.
> THanks.
> Can I connect to SQL server using sql 7 EM? currently it is not allowing
me
> to connect, but some one told me that there is a work around.
> regards,
> Harshal.
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:uTB7Ym9OEHA.2716@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > No, you cant restore a SQL 2000 database backup to SQL 7 due to
> > architectural changes.
> >
> > The otherway from SQL 7 to SQL 2000 is possible.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> > "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> > news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
> > > can i restore sql 2k backup on sql 7?
> > >
> > >
> >
> >
>|||ok .
thanks for the help.
regards,
Harshal.
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:eL44D6%23OEHA.1048@.tk2msftngp13.phx.gbl...
> Hi,
> As far as i know there is no work around to connect SQL 2000 Server using
> SQL 7 server EM.
>
> Thanks
> Hari
> MCDBA
> "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> news:e1zLh39OEHA.736@.tk2msftngp13.phx.gbl...
> > Yeah I knew it just had to confirm.
> > THanks.
> > Can I connect to SQL server using sql 7 EM? currently it is not allowing
> me
> > to connect, but some one told me that there is a work around.
> > regards,
> > Harshal.
> >
> >
> > "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> > news:uTB7Ym9OEHA.2716@.tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > > No, you cant restore a SQL 2000 database backup to SQL 7 due to
> > > architectural changes.
> > >
> > > The otherway from SQL 7 to SQL 2000 is possible.
> > >
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > > "harshal mistry" <harshal_in@.hotmail.com> wrote in message
> > > news:#ZeSOh9OEHA.1512@.TK2MSFTNGP10.phx.gbl...
> > > > can i restore sql 2k backup on sql 7?
> > > >
> > > >
> > >
> > >
> >
> >
>

Restore 225GB database. ASYNC_IO_COMPLETION. (Help! I need this doing by morning) :o)

I am trying to restore a 225GB database using backup exec, but does not seem
to be working. When I look at the processes in SQL one of the restore
processes is displaying ASYNC_IO_COMPLETION, the wait time seems to graduly
rising. As my restores have always worked in the past I've never looked at
the processes, is this normal? Or is this indicating a problem?
thanks in advance
Gav
Hi,
"Ths is normal while restoring a database with large size
The status "ASYNC_IO" comes when the RESTORE process create the blank
database. In your case
the process will stay for some time being you are creating a large database.
FYI, RESTORE process will create a blank database with the exact same file
sizes as the database that is being restored. ASYNCH_IO is the mechanism
used to create a blank database.
I recommend you to execute the restore with STATS option from the Query
Analyzer :-
Restore database <dbname> from disk='c:\dbname.bak' with stats=10
-
Thanks
Hari
MCDBA
"Gav" <gavin.metcalfe@.nospam.btinternet.com> wrote in message
news:cdh8uf$c12$1@.sparta.btinternet.com...
> I am trying to restore a 225GB database using backup exec, but does not
seem
> to be working. When I look at the processes in SQL one of the restore
> processes is displaying ASYNC_IO_COMPLETION, the wait time seems to
graduly
> rising. As my restores have always worked in the past I've never looked at
> the processes, is this normal? Or is this indicating a problem?
> thanks in advance
> Gav
>
|||"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:Ow1SRugbEHA.3596@.tk2msftngp13.phx.gbl...
> Hi,
> "Ths is normal while restoring a database with large size
> The status "ASYNC_IO" comes when the RESTORE process create the blank
> database. In your case
> the process will stay for some time being you are creating a large
database.
> FYI, RESTORE process will create a blank database with the exact same
file[vbcol=seagreen]
> sizes as the database that is being restored. ASYNCH_IO is the mechanism
> used to create a blank database.
> I recommend you to execute the restore with STATS option from the Query
> Analyzer :-
> Restore database <dbname> from disk='c:\dbname.bak' with stats=10
>
> -
> Thanks
> Hari
> MCDBA
> "Gav" <gavin.metcalfe@.nospam.btinternet.com> wrote in message
> news:cdh8uf$c12$1@.sparta.btinternet.com...
> seem
> graduly
at
>
thanks for the info. :o) Turns out the box we were restoring it too was
running a bit slow. We tested a restore of a 15Gb database to test
everything was working correctly and then left the big restore restoring
overnight.
Gav

Restore 225GB database. ASYNC_IO_COMPLETION. (Help! I need this doing by morning) :o)

I am trying to restore a 225GB database using backup exec, but does not seem
to be working. When I look at the processes in SQL one of the restore
processes is displaying ASYNC_IO_COMPLETION, the wait time seems to graduly
rising. As my restores have always worked in the past I've never looked at
the processes, is this normal? Or is this indicating a problem?
thanks in advance
GavHi,
"Ths is normal while restoring a database with large size
The status "ASYNC_IO" comes when the RESTORE process create the blank
database. In your case
the process will stay for some time being you are creating a large database.
FYI, RESTORE process will create a blank database with the exact same file
sizes as the database that is being restored. ASYNCH_IO is the mechanism
used to create a blank database.
I recommend you to execute the restore with STATS option from the Query
Analyzer :-
Restore database <dbname> from disk='c:\dbname.bak' with stats=10
-
Thanks
Hari
MCDBA
"Gav" <gavin.metcalfe@.nospam.btinternet.com> wrote in message
news:cdh8uf$c12$1@.sparta.btinternet.com...
> I am trying to restore a 225GB database using backup exec, but does not
seem
> to be working. When I look at the processes in SQL one of the restore
> processes is displaying ASYNC_IO_COMPLETION, the wait time seems to
graduly
> rising. As my restores have always worked in the past I've never looked at
> the processes, is this normal? Or is this indicating a problem?
> thanks in advance
> Gav
>|||"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:Ow1SRugbEHA.3596@.tk2msftngp13.phx.gbl...
> Hi,
> "Ths is normal while restoring a database with large size
> The status "ASYNC_IO" comes when the RESTORE process create the blank
> database. In your case
> the process will stay for some time being you are creating a large
database.
> FYI, RESTORE process will create a blank database with the exact same
file
> sizes as the database that is being restored. ASYNCH_IO is the mechanism
> used to create a blank database.
> I recommend you to execute the restore with STATS option from the Query
> Analyzer :-
> Restore database <dbname> from disk='c:\dbname.bak' with stats=10
>
> -
> Thanks
> Hari
> MCDBA
> "Gav" <gavin.metcalfe@.nospam.btinternet.com> wrote in message
> news:cdh8uf$c12$1@.sparta.btinternet.com...
> > I am trying to restore a 225GB database using backup exec, but does not
> seem
> > to be working. When I look at the processes in SQL one of the restore
> > processes is displaying ASYNC_IO_COMPLETION, the wait time seems to
> graduly
> > rising. As my restores have always worked in the past I've never looked
at
> > the processes, is this normal? Or is this indicating a problem?
> >
> > thanks in advance
> >
> > Gav
> >
> >
>
thanks for the info. :o) Turns out the box we were restoring it too was
running a bit slow. We tested a restore of a 15Gb database to test
everything was working correctly and then left the big restore restoring
overnight.
Gav

Restore 225GB database. ASYNC_IO_COMPLETION. (Help! I need this doing by morning) :o

I am trying to restore a 225GB database using backup exec, but does not seem
to be working. When I look at the processes in SQL one of the restore
processes is displaying ASYNC_IO_COMPLETION, the wait time seems to graduly
rising. As my restores have always worked in the past I've never looked at
the processes, is this normal? Or is this indicating a problem?
thanks in advance
GavHi,
"Ths is normal while restoring a database with large size
The status "ASYNC_IO" comes when the RESTORE process create the blank
database. In your case
the process will stay for some time being you are creating a large database.
FYI, RESTORE process will create a blank database with the exact same file
sizes as the database that is being restored. ASYNCH_IO is the mechanism
used to create a blank database.
I recommend you to execute the restore with STATS option from the Query
Analyzer :-
Restore database <dbname> from disk='c:\dbname.bak' with stats=10
-
Thanks
Hari
MCDBA
"Gav" <gavin.metcalfe@.nospam.btinternet.com> wrote in message
news:cdh8uf$c12$1@.sparta.btinternet.com...
> I am trying to restore a 225GB database using backup exec, but does not
seem
> to be working. When I look at the processes in SQL one of the restore
> processes is displaying ASYNC_IO_COMPLETION, the wait time seems to
graduly
> rising. As my restores have always worked in the past I've never looked at
> the processes, is this normal? Or is this indicating a problem?
> thanks in advance
> Gav
>|||"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:Ow1SRugbEHA.3596@.tk2msftngp13.phx.gbl...
> Hi,
> "Ths is normal while restoring a database with large size
> The status "ASYNC_IO" comes when the RESTORE process create the blank
> database. In your case
> the process will stay for some time being you are creating a large
database.
> FYI, RESTORE process will create a blank database with the exact same
file
> sizes as the database that is being restored. ASYNCH_IO is the mechanism
> used to create a blank database.
> I recommend you to execute the restore with STATS option from the Query
> Analyzer :-
> Restore database <dbname> from disk='c:\dbname.bak' with stats=10
>
> -
> Thanks
> Hari
> MCDBA
> "Gav" <gavin.metcalfe@.nospam.btinternet.com> wrote in message
> news:cdh8uf$c12$1@.sparta.btinternet.com...
> seem
> graduly
at[vbcol=seagreen]
>
thanks for the info. :o) Turns out the box we were restoring it too was
running a bit slow. We tested a restore of a 15Gb database to test
everything was working correctly and then left the big restore restoring
overnight.
Gav

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.

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.

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.

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.

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.

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!