Restore to different drive

I use Enterprise Manager to backup and restore various SQL Server databases
moving them around on my different dev boxes. I have a case now where a
database is on drive d on one system and it's on drive c on another system.
It won't let me restore to drive C - says I need to use the With Move
option.
I don't see a With Move option in enterprise manager and I don't want to
move a file anyway, I just want to restore it.
Thanks,
TTechnically, the "With Move" option is how SQL implements changing the
restore location of a database. Even if you use Enterprise Mangler to set
up the restores, it is a good idea to read about the BACKUP and RESTORE
commands in BOL (Books On-Line), just so you know what is happening. In
this case, it would have made the error message much clearer.
To use the WITH MOVE option in EM, choose the backup file you want to
restore and any other options that need setting on the General tab. Then
edit the RESTORE AS fields on the Options tab of the restore database popup
to point to the desired file locations.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Tina" <tinamseaburn@.nospammeexcite.com> wrote in message
news:evZhdzLrFHA.1168@.TK2MSFTNGP10.phx.gbl...
>I use Enterprise Manager to backup and restore various SQL Server databases
>moving them around on my different dev boxes. I have a case now where a
>database is on drive d on one system and it's on drive c on another system.
>It won't let me restore to drive C - says I need to use the With Move
>option.
> I don't see a With Move option in enterprise manager and I don't want to
> move a file anyway, I just want to restore it.
> Thanks,
> T
>|||Tina,
When the restore dialog box appears, go to the "options tab" an change
"Restore As" for each file. If they are pointing to "D" and the server does
not have "D" drive or the specified folder does not exosts in the "D" drive,
then you have to change this arguments.
AMB
"Tina" wrote:
> I use Enterprise Manager to backup and restore various SQL Server databases
> moving them around on my different dev boxes. I have a case now where a
> database is on drive d on one system and it's on drive c on another system.
> It won't let me restore to drive C - says I need to use the With Move
> option.
> I don't see a With Move option in enterprise manager and I don't want to
> move a file anyway, I just want to restore it.
> Thanks,
> T
>
>

Restore SQL 2000 different domain?

Hello. Would anyone know of the most advisable method in moving our SQL
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
J
Hi
"J" wrote:

> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546

> Thanks in advance.
> J
John
|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>
> John

Restore SQL 2000 different domain?

Hello. Would anyone know of the most advisable method in moving our SQL
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
JHi
"J" wrote:
> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546
> Thanks in advance.
> J
John|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
>> Hello. Would anyone know of the most advisable method in moving our SQL
>> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
>> retiring ServerA and ServerB will take on the same name and IP address as
>> ServerA? I'm mainly wondering since we have some windows authentication
>> logins on our SQL Server and moving it to a different domain/machine
>> would
>> affect anything.
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>> Thanks in advance.
>> J
> John

Restore SQL 2000 different domain?

Hello. Would anyone know of the most advisable method in moving our SQL
2000 on ServerA to another SQL 2000 machine ServerB where we plan on
retiring ServerA and ServerB will take on the same name and IP address as
ServerA? I'm mainly wondering since we have some windows authentication
logins on our SQL Server and moving it to a different domain/machine would
affect anything.
Thanks in advance.
JHi
"J" wrote:

> Hello. Would anyone know of the most advisable method in moving our SQL
> 2000 on ServerA to another SQL 2000 machine ServerB where we plan on
> retiring ServerA and ServerB will take on the same name and IP address as
> ServerA? I'm mainly wondering since we have some windows authentication
> logins on our SQL Server and moving it to a different domain/machine would
> affect anything.
>
See http://support.microsoft.com/kb/246133/ on how to transfer logins from
one server to another.
If you rename the server you will need to drop it and re-add it. See
http://support.microsoft.com/kb/303774/
General information about moving databases see
http://support.microsoft.com/kb/314546

> Thanks in advance.
> J
John|||Thanks for the info. Much appreciated.
Take care.
J
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FC96D7E6-AEC9-4CC7-8602-75B61F1F571E@.microsoft.com...
> Hi
> "J" wrote:
>
> See http://support.microsoft.com/kb/246133/ on how to transfer logins from
> one server to another.
> If you rename the server you will need to drop it and re-add it. See
> http://support.microsoft.com/kb/303774/
> General information about moving databases see
> http://support.microsoft.com/kb/314546
>
> Johnsql

Restore of users when moving a database from one server to another...

Hi
When moving a SQL server database from one server to another you get
problem with the users.
Is there a easy way to recreate or fix the users that the database
allready contains or do I need to remove all security settings and
reapply them?
Thanks
/MagnusHi
You can create a Script about the database users and execute this when you restore database. Initially you should erase the users that has the new database and subsequently to execute the script in the Query analyzer
The Script you can create for Enterprise Manager, Rigth Click about the database, All Task, Generate SQL Script
*********************************************************
When moving a SQL server database from one server to another you ge
problem with the users
Is there a easy way to recreate or fix the users that the databas
allready contains or do I need to remove all security settings an
reapply them|||Look at sp_change_users_login in BOL.
Mike Abraham
"Magnus Wettemark" <magnus.wettemark@.staffware.dk> wrote in message
news:ec837e09.0402110332.3f9d9f17@.posting.google.com...
> Hi
> When moving a SQL server database from one server to another you get
> problem with the users.
> Is there a easy way to recreate or fix the users that the database
> allready contains or do I need to remove all security settings and
> reapply them?
> Thanks
> /Magnus

Restore of users when moving a database from one server to another...

Hi
When moving a SQL server database from one server to another you get
problem with the users.
Is there a easy way to recreate or fix the users that the database
allready contains or do I need to remove all security settings and
reapply them?
Thanks
/MagnusHi.
You can create a Script about the database users and execute this when you r
estore database. Initially you should erase the users that has the new datab
ase and subsequently to execute the script in the Query analyzer.
The Script you can create for Enterprise Manager, Rigth Click about the data
base, All Task, Generate SQL Script.
****************************************
******************
When moving a SQL server database from one server to another you get
problem with the users.
Is there a easy way to recreate or fix the users that the database
allready contains or do I need to remove all security settings and
reapply them?|||Look at sp_change_users_login in BOL.
Mike Abraham
"Magnus Wettemark" <magnus.wettemark@.staffware.dk> wrote in message
news:ec837e09.0402110332.3f9d9f17@.posting.google.com...
> Hi
> When moving a SQL server database from one server to another you get
> problem with the users.
> Is there a easy way to recreate or fix the users that the database
> allready contains or do I need to remove all security settings and
> reapply them?
> Thanks
> /Magnus

Restore MSDB

A quick question on MSDB and database backups:
We're moving one database to another. This database has a ton of jobs
associated with it. W're going ot be moving this database to a fresh install
of SQL Server.
My question is: if I wanted to maintain the jobs that I've created, would
just backing up MSDB and restoring it to the new box keep those jobs intact?
Would there be any issues with datqabase id's, etc. getting screwed up or ar
e
we good to go with just the restore of MSDB?
Thanks!!If you know the jobs that is associated to this database, you can generate
the SQL scripts for those jobs and run the script on the new server.
"A. Robinson" wrote:

> A quick question on MSDB and database backups:
> We're moving one database to another. This database has a ton of jobs
> associated with it. W're going ot be moving this database to a fresh insta
ll
> of SQL Server.
> My question is: if I wanted to maintain the jobs that I've created, would
> just backing up MSDB and restoring it to the new box keep those jobs intac
t?
> Would there be any issues with datqabase id's, etc. getting screwed up or
are
> we good to go with just the restore of MSDB?
> Thanks!!

Restore Messed Up Table Names

Using SQL Server 2000 and moving to a new computer. We did a full backup of
the existing database to tape, brought up the new computer with a clean
install using the same server name and IP address, and did a full restore.
Not only were some permissions messed up, but Crystal Reports 10 and some
Access Data Projects refused to run. I finally discovered while running an
SP_WHO that the individual database names that we'd created (meaning not
'master' and the other standard tables) had several dozen blanks appended
onto the end of them. Looking at dbnames in the SP_WHO made it clear that
this had happened, and once I knew what I was looking for it was apparent in
Enterprise Manager as well when I'd select a database name in the left pane.
Interestingly, VB6 applications have no trouble connecting to these tables
without modification of the connection string. Every single CR10 report so
far has had to have it's tables relinked, and this has broken some other
code that looks at dbnames.

1: How could something like this happen?

2: How is it best fixed?

Thanks!
DavidDavid C. Barber (david@.NOSPAMdbarber.com) writes:

Quote:

Originally Posted by

Using SQL Server 2000 and moving to a new computer. We did a full
backup of the existing database to tape, brought up the new computer
with a clean install using the same server name and IP address, and did
a full restore. Not only were some permissions messed up, but Crystal
Reports 10 and some Access Data Projects refused to run. I finally
discovered while running an SP_WHO that the individual database names
that we'd created (meaning not 'master' and the other standard tables)
had several dozen blanks appended onto the end of them. Looking at
dbnames in the SP_WHO made it clear that this had happened, and once I
knew what I was looking for it was apparent in Enterprise Manager as
well when I'd select a database name in the left pane. Interestingly,
VB6 applications have no trouble connecting to these tables without
modification of the connection string. Every single CR10 report so far
has had to have it's tables relinked, and this has broken some other
code that looks at dbnames.
>
1: How could something like this happen?
>
2: How is it best fixed?

I'm a little confused. You first say "existing database" in singular,
and then you say "individual database names" in plural. Your subject
talks about messed up table names, but table names do not display in
sp_who. Then again, you call master a table.

I'm sorry if I'm picky, but if I don't understand what you mean, it's
difficult to answer. But I try to address it as good as I can:

1) If the database are messed up, this is probably because you added
the spaces when you restored the databases on the new server. The
database names are not carried over from the old server. Or did you
copy master too?

2) If the table names have been altered this would be very strange.
I would even say that it is impossible.

3) What typically does gets messed up when you move databases like this
is the mapping between server logins and database users. This can easily
be examined with sp_helpuser. If you have a random mapping, then you
have this problem. The stored procedure sp_changes_users_login can
be used to address this.

--
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|||"Erland Sommarskog" <esquel@.sommarskog.sewrote in message
news:Xns9832738788829Yazorman@.127.0.0.1...

Quote:

Originally Posted by

David C. Barber (david@.NOSPAMdbarber.com) writes:

Quote:

Originally Posted by

Using SQL Server 2000 and moving to a new computer. We did a full
backup of the existing database to tape, brought up the new computer
with a clean install using the same server name and IP address, and did
a full restore. Not only were some permissions messed up, but Crystal
Reports 10 and some Access Data Projects refused to run. I finally
discovered while running an SP_WHO that the individual database names
that we'd created (meaning not 'master' and the other standard tables)
had several dozen blanks appended onto the end of them. Looking at
dbnames in the SP_WHO made it clear that this had happened, and once I
knew what I was looking for it was apparent in Enterprise Manager as
well when I'd select a database name in the left pane. Interestingly,
VB6 applications have no trouble connecting to these tables without
modification of the connection string. Every single CR10 report so far
has had to have it's tables relinked, and this has broken some other
code that looks at dbnames.

1: How could something like this happen?

2: How is it best fixed?

>
I'm a little confused. You first say "existing database" in singular,
and then you say "individual database names" in plural. Your subject
talks about messed up table names, but table names do not display in
sp_who. Then again, you call master a table.
>
I'm sorry if I'm picky, but if I don't understand what you mean, it's
difficult to answer. But I try to address it as good as I can:
>
1) If the database are messed up, this is probably because you added
the spaces when you restored the databases on the new server. The
database names are not carried over from the old server. Or did you
copy master too?
>
2) If the table names have been altered this would be very strange.
I would even say that it is impossible.
>
3) What typically does gets messed up when you move databases like this
is the mapping between server logins and database users. This can easily
be examined with sp_helpuser. If you have a random mapping, then you
have this problem. The stored procedure sp_changes_users_login can
be used to address this.

Sorry that I wasn't more clear before. Comes of being in too much of a
hurry.

We were upgrading the server hardware for our SQL Server 2000.

We backed up the entire existing server as a full backup.

We installed the new hardware and software, named the new server to be
identical to the old server which was taken off-line entirely.

We used the same IP address with the new server box.

We did a full restore of the backed up server databases.

The resulting individual databases, except for the standard ones like master
that are created by SQL Server itself all restored with several dozen blanks
appended to the end of the existing database name, which appears to break
Crystal Reports 10, Access Data Projects, and some VB6 code, although not
the basic connection to the database using VB6.

We don't know why this happened, nor the best way(s) to fix it.

David|||David C. Barber (david@.NOSPAMdbarber.com) writes:

Quote:

Originally Posted by

We were upgrading the server hardware for our SQL Server 2000.
>
We backed up the entire existing server as a full backup.

So you backed all files on the server with Windows backup, and you did not
backup the individual databases through SQL Servers own BACKUP command?

Did you stop SQL Server prior to starting this backup?

Quote:

Originally Posted by

The resulting individual databases, except for the standard ones like
master that are created by SQL Server itself all restored with several
dozen blanks appended to the end of the existing database name, which
appears to break Crystal Reports 10, Access Data Projects, and some VB6
code, although not the basic connection to the database using VB6.

Could you post the output of this query:

SELECT len(name), datalength(name)/2, name
FROM master..sysdatabases
ORDER BY name

Is the old hardware available, so you can start it, and run the same
query there?

--
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