Restoring to New server

I have created a new server running sql server 6.5 and I am trying to restore a databasefrm an existing 6.5 server to this new server . I got the master on but I cannot get any of the databases on. First the database was going in suspend mode, then after I resolved that I am getting size errors that I cannot seem to resolve even with expanding the devices.

What I'm I doing wrong? Did I miss a step? or is there a problem with the server setup?

Ans..Q1 What I'm I doing wrong?

A1 Maybe nothing (insufficient information).

Was the master backup used in the restore to the second server in fact current (assuming the restores (DB Loads) were performed to similar devices on the new server - using similar device orders, sizes and types, as those of the DB devices as they existed on the original server)? If not, some device data may be incorrect (most likely, incomplete). In that case it may be possible to use Disk ReInit for each device on the new server as necessary to address the issue (using the same logical and physical device names is easier if that is the case; however the 2k block size value entered for the size parameter must be the same as the production user devices at the times their backup dumps were taken.). Once complete, run Disk ReFit.

Q2 Did I miss a step?

A2 Maybe, maybe not (insufficient information). However, do make sure both servers have:
similar character set installs (collation),
similar service pack levels applied,
similar database device geometries.

Q3 or is there a problem with the server setup?

A3 To help rule out some potential issues with the server setup, do a dump and load of Pubs on the new server; if Pubs restores without issues, the basic server configuration is probably not the main issue.

Restoring to new database doesn't default DB file names

In SQL 2000 EM, when you restore a database from an existing database backup but specify a new database name to restore to, the filenames are automatically updated to match the new name of the database that will be restored.

I tried to do this with SQL 2005 Management Studio but it appears that the filenames aren't updated i.e. they are the same as the original database filenames. Do i have to manually go and change the filenames to reflect the fact that I'm creating a new database via a restore? If so, why doesn't the behaiour follow that of SQL 2000?

Thanks

Hello there

This is by design in SQL Server 2005.

There are two ways to restore to a new database:
1- By launching the restore database dialog from the context of an existing database. This would pre-load the existing backup set. You could change the database name & the dialog would automatically change the DB filenames for you.

2- By launching the resotore database from the 'Databases' node & later specifying the backup set by selecting a backup file thru 'device' option.

#1 above should work fine when you change the database name & hit 'Ok'

#2 above doesn't automatically change the DB file names for you. This is by design in SQL Server 2005. In SQL Server 2000 too, you had to go to the 'options' page for the dialog to automatically change file names.

The grid on the options page in SQL Server 2005's restore dialog is editable. You could directly edit the file names in the grid to accomplish the action.

Thanks,

Restoring database question plz help!

Here is the question if i reinstall sql server 2000 ent can i use my full back up file to reproduce all of my prior existing database and do i need the data file like the .ldf, .mdf, .ndf to do this and if so i do i do this without the data filesYour backup file should be all you need to restore your database to the moment that it was backed up. You will need to restore log files to recover any changes since the backup was made.
You should test your backup/restore plan first to make sure it works and you know how to do it before you wipe out your current installation!|||OK thanx but i cant test this because my sql server service doesnt want to start and i have admin rights. it givin me a unexpected error is the best thing here to reinstall sql server and then restore the back up file.|||basically rebuild the ole thing again.

Restoring database problem

While restoring backup from ad.bak file to already existing database followi
ng error is appeared "Cannot find file Id 2 on device C:\dbBackup\ad.bak ba
ckup or restore operation terminated abnormally " This is happened when i tr
y to restore database.Hi
Can you show us your RESTORE command?
"nadeem" <anonymous@.discussions.microsoft.com> wrote in message
news:CE62DBDE-C168-49B1-BB42-F89B1881A438@.microsoft.com...
> While restoring backup from ad.bak file to already existing database
following error is appeared "Cannot find file Id 2 on device
C:\dbBackup\ad.bak backup or restore operation terminated abnormally " This
is happened when i try to restore database.|||Hi,
You can use the RESTORE HEADERONLY command to idenfify the backup file list
and use RESTORE DATABASE to restore the specific file.
Sample code
RESTORE HEADERONLY FROM DISK='c:\backup\dbname.bak'
RESTORE DATABASE mydatabase FROM DISK='C:\backup\dbname.bak' WITH FILE =
FileNumber
(Use option MOVE if you have the database already in the same server)
Thanks
Hari
MCDBA
"nadeem" <anonymous@.discussions.microsoft.com> wrote in message
news:CE62DBDE-C168-49B1-BB42-F89B1881A438@.microsoft.com...
> While restoring backup from ad.bak file to already existing database
following error is appeared "Cannot find file Id 2 on device
C:\dbBackup\ad.bak backup or restore operation terminated abnormally " This
is happened when i try to restore database.

Restoring database over existing database and full-text catlog integrity

I know that if you have to drop a full-text enable database and restore it,
you will have to rebuild the full-text indexes. My question is, if you have
a database where the data has not changed since your last backup and you
restore over top of the existing database, is the full-text index's
integrity okay?
I have recently restored a large full-text enabled database over top of an
existing one after an upgrade failed and the full-text appears to be intact.
I can run full-text searches. Does anyone know if there are any potential
issues? The table has about 28 million rows and the full-text rebuild would
take days so I am trying to avoid that.
Thanks,
~Travis
Yes, this should work fine.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Travis Nordrum" <tnordrum@.krollontrack.com> wrote in message
news:%23BH%23WEX9FHA.3048@.TK2MSFTNGP10.phx.gbl...
>I know that if you have to drop a full-text enable database and restore it,
>you will have to rebuild the full-text indexes. My question is, if you
>have a database where the data has not changed since your last backup and
>you restore over top of the existing database, is the full-text index's
>integrity okay?
> I have recently restored a large full-text enabled database over top of an
> existing one after an upgrade failed and the full-text appears to be
> intact. I can run full-text searches. Does anyone know if there are any
> potential issues? The table has about 28 million rows and the full-text
> rebuild would take days so I am trying to avoid that.
> Thanks,
> ~Travis
>
|||Thanks.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ecSzEWf9FHA.3772@.TK2MSFTNGP10.phx.gbl...
> Yes, this should work fine.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Travis Nordrum" <tnordrum@.krollontrack.com> wrote in message
> news:%23BH%23WEX9FHA.3048@.TK2MSFTNGP10.phx.gbl...
>