restore db without the log?

Is it possible in sql2k to restore a db without restoring the transaction
log? If so, how?
TIA, ChrisR
Hi,
If you have the FULL Database backup you could restore the full database.
See RESTORE DATABASE command in books online.
Log restore will help you to recover the database till POINT IN TIME.
Thanks
Hari
SQL Server MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:OMubP%23LiFHA.3476@.TK2MSFTNGP10.phx.gbl...
> Is it possible in sql2k to restore a db without restoring the transaction
> log? If so, how?
> TIA, ChrisR
>
|||Hari, I have a FULL backup and want to restore the full db, minus the 20 gig
transaction log.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ezKnNAMiFHA.392@.TK2MSFTNGP10.phx.gbl...
> Hi,
> If you have the FULL Database backup you could restore the full database.
> See RESTORE DATABASE command in books online.
> Log restore will help you to recover the database till POINT IN TIME.
> Thanks
> Hari
> SQL Server MVP
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OMubP%23LiFHA.3476@.TK2MSFTNGP10.phx.gbl...
>
|||If you mean without creating the transaction log file then no. The restore
process from a FULL backup will always rebuild the db and log files exactly
as they were when you made the backup. You can detach the db and attach it
with sing_file_db and it will create a new log file. I am not sure how
large it makes the new file though. It's probably the size you originally
created it at or explicitly did an alter file on it.
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:%23dKNBNMiFHA.3716@.TK2MSFTNGP14.phx.gbl...
> Hari, I have a FULL backup and want to restore the full db, minus the 20
> gig transaction log.
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:ezKnNAMiFHA.392@.TK2MSFTNGP10.phx.gbl...
>

restore db without the log?

Is it possible in sql2k to restore a db without restoring the transaction
log? If so, how?
TIA, ChrisRHi,
If you have the FULL Database backup you could restore the full database.
See RESTORE DATABASE command in books online.
Log restore will help you to recover the database till POINT IN TIME.
Thanks
Hari
SQL Server MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:OMubP%23LiFHA.3476@.TK2MSFTNGP10.phx.gbl...
> Is it possible in sql2k to restore a db without restoring the transaction
> log? If so, how?
> TIA, ChrisR
>|||Hari, I have a FULL backup and want to restore the full db, minus the 20 gig
transaction log.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ezKnNAMiFHA.392@.TK2MSFTNGP10.phx.gbl...
> Hi,
> If you have the FULL Database backup you could restore the full database.
> See RESTORE DATABASE command in books online.
> Log restore will help you to recover the database till POINT IN TIME.
> Thanks
> Hari
> SQL Server MVP
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OMubP%23LiFHA.3476@.TK2MSFTNGP10.phx.gbl...
>> Is it possible in sql2k to restore a db without restoring the transaction
>> log? If so, how?
>> TIA, ChrisR
>|||If you mean without creating the transaction log file then no. The restore
process from a FULL backup will always rebuild the db and log files exactly
as they were when you made the backup. You can detach the db and attach it
with sing_file_db and it will create a new log file. I am not sure how
large it makes the new file though. It's probably the size you originally
created it at or explicitly did an alter file on it.
--
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:%23dKNBNMiFHA.3716@.TK2MSFTNGP14.phx.gbl...
> Hari, I have a FULL backup and want to restore the full db, minus the 20
> gig transaction log.
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:ezKnNAMiFHA.392@.TK2MSFTNGP10.phx.gbl...
>> Hi,
>> If you have the FULL Database backup you could restore the full database.
>> See RESTORE DATABASE command in books online.
>> Log restore will help you to recover the database till POINT IN TIME.
>> Thanks
>> Hari
>> SQL Server MVP
>> "ChrisR" <noemail@.bla.com> wrote in message
>> news:OMubP%23LiFHA.3476@.TK2MSFTNGP10.phx.gbl...
>> Is it possible in sql2k to restore a db without restoring the
>> transaction log? If so, how?
>> TIA, ChrisR
>>
>

restore db without the log?

Is it possible in sql2k to restore a db without restoring the transaction
log? If so, how?
TIA, ChrisRHi,
If you have the FULL Database backup you could restore the full database.
See RESTORE DATABASE command in books online.
Log restore will help you to recover the database till POINT IN TIME.
Thanks
Hari
SQL Server MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:OMubP%23LiFHA.3476@.TK2MSFTNGP10.phx.gbl...
> Is it possible in sql2k to restore a db without restoring the transaction
> log? If so, how?
> TIA, ChrisR
>|||Hari, I have a FULL backup and want to restore the full db, minus the 20 gig
transaction log.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:ezKnNAMiFHA.392@.TK2MSFTNGP10.phx.gbl...
> Hi,
> If you have the FULL Database backup you could restore the full database.
> See RESTORE DATABASE command in books online.
> Log restore will help you to recover the database till POINT IN TIME.
> Thanks
> Hari
> SQL Server MVP
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OMubP%23LiFHA.3476@.TK2MSFTNGP10.phx.gbl...
>|||If you mean without creating the transaction log file then no. The restore
process from a FULL backup will always rebuild the db and log files exactly
as they were when you made the backup. You can detach the db and attach it
with sing_file_db and it will create a new log file. I am not sure how
large it makes the new file though. It's probably the size you originally
created it at or explicitly did an alter file on it.
Andrew J. Kelly SQL MVP
"ChrisR" <noemail@.bla.com> wrote in message
news:%23dKNBNMiFHA.3716@.TK2MSFTNGP14.phx.gbl...
> Hari, I have a FULL backup and want to restore the full db, minus the 20
> gig transaction log.
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:ezKnNAMiFHA.392@.TK2MSFTNGP10.phx.gbl...
>sql

Restore DB to sql 2k

After restoring a db from SQL 7.0 running on a Win98
system (English version) to a SQL 2000 on an XP system
(Spanish version) I get the following message on a stored
procedure:
Server: Msg 446, Level 16, State 9, Procedure
sp_RptPartida, Line 33
Cannot resolve collation conflict for equal to operation.
I did not get such message in the old system. Is there a
way to avoid it. I need to be able to maintain the db on
my client (they have sql 7.0) and I wish to do the
development on sql 2000.There is a conflict in collations between your Charcter table attributes
that you are comparing
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_da-db_7ory.asp
http://tinyurl.com/3dr2j
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Mauricio" <macs01@.telesal.net> wrote in message
news:036f01c3cb24$72727230$a001280a@.phx.gbl...
> After restoring a db from SQL 7.0 running on a Win98
> system (English version) to a SQL 2000 on an XP system
> (Spanish version) I get the following message on a stored
> procedure:
> Server: Msg 446, Level 16, State 9, Procedure
> sp_RptPartida, Line 33
> Cannot resolve collation conflict for equal to operation.
> I did not get such message in the old system. Is there a
> way to avoid it. I need to be able to maintain the db on
> my client (they have sql 7.0) and I wish to do the
> development on sql 2000.

Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (It
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.
I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:

> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use." (It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.
|||Next time, use sp_who to see who is using the database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...[vbcol=seagreen]
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:

Restore db to another server

I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
(SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
I'm restoring db from tape w. BackupExec 9.0. The first time I did a restore
it was cancelled after 10% write; error 34113 on BackupExec server, and
repeated error 57859 on destination SQL server.
When rerun job, no data is written and job cancels with same error in
BackupExec server, and new error in destination SQL server: 57859 --
"Exclusive access couldn not be obtained because the database is in use." (I
t
seems to me it's not in use, nobody uses this server yet.)
Strange thing is, I can restore another (test) database from same tape
without any problems.
Happy to get any hints or guidelines, I'm kinda stuck.I deleted the restored database on new SQL server an reran the restore job,
and everything worked OK -- and so I will never know what went wrong the
first time, but will nevertheless be able to spend the weekend with family
instead of SQL.
Thanks for taking time, if you took any.
"JSL" wrote:

> I'm in the process of migrating db:s from SQL 2000 (SP2) on Windows 2000
> (SP4) to SQL 2000 (SP4) on Windows Server 2003 (SP1).
> I'm restoring db from tape w. BackupExec 9.0. The first time I did a resto
re
> it was cancelled after 10% write; error 34113 on BackupExec server, and
> repeated error 57859 on destination SQL server.
> When rerun job, no data is written and job cancels with same error in
> BackupExec server, and new error in destination SQL server: 57859 --
> "Exclusive access couldn not be obtained because the database is in use."
(It
> seems to me it's not in use, nobody uses this server yet.)
> Strange thing is, I can restore another (test) database from same tape
> without any problems.
> Happy to get any hints or guidelines, I'm kinda stuck.|||Next time, use sp_who to see who is using the database.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JSL" <JSL@.discussions.microsoft.com> wrote in message
news:90762CE8-604D-4BD5-A1DE-9645952022C9@.microsoft.com...[vbcol=seagreen]
>I deleted the restored database on new SQL server an reran the restore job,
> and everything worked OK -- and so I will never know what went wrong the
> first time, but will nevertheless be able to spend the weekend with family
> instead of SQL.
> Thanks for taking time, if you took any.
> "JSL" wrote:
>sql

Restore db and logs from device to a point in time

When restoring a database and log files from a device the point in time
option disappears. How do I restore from a device to a point in time? Is
there an easy way to restore multiple logs from a device? It seems like
doing them one at a time is the only option and it's quite a pain.I recommend that you familiar yourself with the RESTORE command so you can
do this from Query Analyzer.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"David Morrison" <me@.nospam.com> wrote in message
news:uof2WquuDHA.1596@.TK2MSFTNGP10.phx.gbl...
> When restoring a database and log files from a device the point in time
> option disappears. How do I restore from a device to a point in time? Is
> there an easy way to restore multiple logs from a device? It seems like
> doing them one at a time is the only option and it's quite a pain.
>

Restore database without Tran Log

Can I restore a user created database, from a normal SQL Server Full backup,
without restoring the log? My problem is that I have a user who backed up a
database, deleted it, and now has to restore it again (on another server,
when the old server no longer exists) that doesn't have enough disk space to
accomindate the transaction log.
Thanks in advance.
PaulSQL Server will create the transaction log the size it need to, when you
issue the restore. My experience is that it will be the same as when you did
the backup, but I can imagine that it can potentially grow during the
restore operation (pure speculation here).
However, this is not anything you can influence. Just run RESTORE
FILELISTONY and make sure you have the amount of disk that it reports (sum
the files). Note that you can use the MOVE option to specify some other
disk(/path) for any of the files.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Paul Bergstedt" <Paul@.nospam.com> wrote in message
news:OF5ykqP5DHA.2064@.TK2MSFTNGP11.phx.gbl...

quote:

---

> Can I restore a user created database, from a normal SQL Server Full

---

backup,

quote:

---

> without restoring the log? My problem is that I have a user who backed up

---

a

quote:

---

> database, deleted it, and now has to restore it again (on another server,
> when the old server no longer exists) that doesn't have enough disk space

---

to

quote:

---

> accomindate the transaction log.
> Thanks in advance.
> Paul
>

---

|||Unfortunately, he doesn't have enough disk to restore to the original
transaction log file size on any drive. The only solution I can think of is
to do a filegroup restore with NORECOVERY. Set database status = 32768, or
Emergency Mode, restarted SQL Server. Create another database, and use DDL
scripts and DTS packages to transfer over all the objects. If there is a
cleaner way to do it, I would like to know.
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:utD36vP5DHA.2580@.TK2MSFTNGP11.phx.gbl...

quote:

---

> SQL Server will create the transaction log the size it need to, when you
> issue the restore. My experience is that it will be the same as when you

---

did

quote:

---

> the backup, but I can imagine that it can potentially grow during the
> restore operation (pure speculation here).
> However, this is not anything you can influence. Just run RESTORE
> FILELISTONY and make sure you have the amount of disk that it reports (sum
> the files). Note that you can use the MOVE option to specify some other
> disk(/path) for any of the files.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>

---

http://groups.google.com/groups?oi=...ublic.sqlserver

quote:

---

>
> "Paul Bergstedt" <Paul@.nospam.com> wrote in message
> news:OF5ykqP5DHA.2064@.TK2MSFTNGP11.phx.gbl...
> backup,
up[QUOTE]
> a
server,[QUOTE]
space[QUOTE]
> to
>

---

Restore database without Tran Log

Can I restore a user created database, from a normal SQL Server Full backup,
without restoring the log? My problem is that I have a user who backed up a
database, deleted it, and now has to restore it again (on another server,
when the old server no longer exists) that doesn't have enough disk space to
accomindate the transaction log.
Thanks in advance.
PaulSQL Server will create the transaction log the size it need to, when you
issue the restore. My experience is that it will be the same as when you did
the backup, but I can imagine that it can potentially grow during the
restore operation (pure speculation here).
However, this is not anything you can influence. Just run RESTORE
FILELISTONY and make sure you have the amount of disk that it reports (sum
the files). Note that you can use the MOVE option to specify some other
disk(/path) for any of the files.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Paul Bergstedt" <Paul@.nospam.com> wrote in message
news:OF5ykqP5DHA.2064@.TK2MSFTNGP11.phx.gbl...
> Can I restore a user created database, from a normal SQL Server Full
backup,
> without restoring the log? My problem is that I have a user who backed up
a
> database, deleted it, and now has to restore it again (on another server,
> when the old server no longer exists) that doesn't have enough disk space
to
> accomindate the transaction log.
> Thanks in advance.
> Paul
>|||Unfortunately, he doesn't have enough disk to restore to the original
transaction log file size on any drive. The only solution I can think of is
to do a filegroup restore with NORECOVERY. Set database status = 32768, or
Emergency Mode, restarted SQL Server. Create another database, and use DDL
scripts and DTS packages to transfer over all the objects. If there is a
cleaner way to do it, I would like to know.
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:utD36vP5DHA.2580@.TK2MSFTNGP11.phx.gbl...
> SQL Server will create the transaction log the size it need to, when you
> issue the restore. My experience is that it will be the same as when you
did
> the backup, but I can imagine that it can potentially grow during the
> restore operation (pure speculation here).
> However, this is not anything you can influence. Just run RESTORE
> FILELISTONY and make sure you have the amount of disk that it reports (sum
> the files). Note that you can use the MOVE option to specify some other
> disk(/path) for any of the files.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Paul Bergstedt" <Paul@.nospam.com> wrote in message
> news:OF5ykqP5DHA.2064@.TK2MSFTNGP11.phx.gbl...
> > Can I restore a user created database, from a normal SQL Server Full
> backup,
> > without restoring the log? My problem is that I have a user who backed
up
> a
> > database, deleted it, and now has to restore it again (on another
server,
> > when the old server no longer exists) that doesn't have enough disk
space
> to
> > accomindate the transaction log.
> >
> > Thanks in advance.
> >
> > Paul
> >
> >
>

restore database users-logins mapping lost

i have a DB with DB users that are mapped to server logins
after backing the databasr and restoring on other server (with the same
logins defined)
the logins are not mapped to the sql user
wanting to do this from the security folder in enterprise manager, pressing
the login
in database access tab checking the required checkbox for the newly restored
database
(and the DB user correct name mapping appears)
pressing OK button gives the error Error 21002: [SQL-DMO]User 'appUser'
already exists.
what is the best way to achive the mapping from the login to the user
without deleteing anything and re-defining database permissions for the
user?
thanks.
My preference is to use sp_SidMap. You can get it here
http://download.microsoft.com/downlo...us/Mapsids.exe
The accompanying KB article is here
INF: How to Resolve Permission Issues When a Database is Moved Between SQL
Servers
http://support.microsoft.com/default...;en-us;Q240872
Some other KB articles that may be useful are
PRB: User Logon and/or Permission Errors After Restoring Dump
http://support.microsoft.com/default...;en-us;Q168001
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/default...;en-us;Q274188
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"z f" <nospam@.nospam.com> wrote in message
news:eJ2jd$LWGHA.4484@.TK2MSFTNGP02.phx.gbl...
>i have a DB with DB users that are mapped to server logins
> after backing the databasr and restoring on other server (with the same
> logins defined)
> the logins are not mapped to the sql user
> wanting to do this from the security folder in enterprise manager,
> pressing the login
> in database access tab checking the required checkbox for the newly
> restored database
> (and the DB user correct name mapping appears)
> pressing OK button gives the error Error 21002: [SQL-DMO]User 'appUser'
> already exists.
> what is the best way to achive the mapping from the login to the user
> without deleteing anything and re-defining database permissions for the
> user?
> thanks.
>
>
>
|||http://www.databasejournal.com/featu...le.php/2228611
http://vyaskn.tripod.com/troubleshoo...phan_users.htm
|||Sorry meant to type a little description as well =P First link is for
migrating users from one server to another, It will create a script of
the accounts on the old server that you can run on the new server which
will create the correct sids etc.. so when you roll over a database
from the server1 to server2, u wont have orphaned users in the db on
server2 that dont have physical sql logins associated with them. That
should fix your problem. Make sure if youve added new users server2 to
remove them before running the script on server2 after u have it
created on server1 from the first link above
|||thanks
it is a killer script for me
i found something simpler:
sp_change_users_login (built in with SQL Server)
where did it hide?
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:%23hf6DFMWGHA.1228@.TK2MSFTNGP02.phx.gbl...
> My preference is to use sp_SidMap. You can get it here
> http://download.microsoft.com/downlo...us/Mapsids.exe
> The accompanying KB article is here
> INF: How to Resolve Permission Issues When a Database is Moved Between SQL
> Servers
> http://support.microsoft.com/default...;en-us;Q240872
> Some other KB articles that may be useful are
> PRB: User Logon and/or Permission Errors After Restoring Dump
> http://support.microsoft.com/default...;en-us;Q168001
> PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
> http://support.microsoft.com/default...;en-us;Q274188
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
>
> "z f" <nospam@.nospam.com> wrote in message
> news:eJ2jd$LWGHA.4484@.TK2MSFTNGP02.phx.gbl...
>

Restore Database Question

Hello There,

I have a question about Restoring a database. How do I restore an existing Backup file of a database to a different database ?

For example, I have a backup file "a.bak", of the database name "a". This database has original file names as "a_data.mdf" and "a_log.ldf".

Can I restore this bak up file to a new database, say "b" which would have corresponding original file name as "b_data.mdf" and "b_log.ldf" ?

Please show me how to do this with window interface, if you can.

I would appreciate very much.

-pnnIn Enterprise Manager, right-click on Databases and select All Tasks, Restore Database.
In the Restore as database box, enter a new database name, or the name of the db you want to overwrite.
Select Restore: From device. Click Select Devices. If there is a device listed, click the Remove button (this doesn' actually affect the device!). Not click the Add button and browse/select the database file you want to restore.
Back out ot the first dialog, then go to the options tab.
Your logical file names can remain the same, but your physical file names should already have the name of your new database.
Make sure the Recover completion state option is set to leave the database operational, and then click OK.

Let us know if you have any other questions about this. Don't sweat it, because its very routine.

blindman|||Thank you for your prompt response!

You are NOT BLIND at all, Blind Man ! You're great !|||hi!

our company used to have our web site (and the DB) hosted and managed by our vendor. we are now in the process of migrating it to our in house servers.

so i need to migrate the DB too (SQL Server). so far i got .bak file. do i need any other files to restore the db (like .mdf, etc)?

thanks,
JN.|||your .BAK file is all you need. But I would consider making backups of your system db's as well, unless you have no DTS packages, scheduled tasks, backup history to care for, and logins.|||i'm getting this error (attached).|||jnurbek,
Complete the tasks that blindman posted.

It is possible that the database is trying to restore to a drive location that is not valid.

Regards|||All that error is telling you is that you are trying to restore a database that has a different location for the log and data files than the destination database has. Example: if I had

db1
data file - c:\db1.mdf
log file - c:\db1.ldf

and tried to restore a database that was

db2
data file - d:\db2.mdf
log file - d:\db2.ldf

it would give me your error, it tells you what you need to do by saying use the "with move" option.

For the above example you would write

RESTORE DATABASE db1
FROM DISK= 'wherever you have your backupfile.bak'
WITH RECOVERY,replace,
MOVE 'db2_data'
TO 'c:\db1.mdf',
MOVE db2_log'
TO 'c:\db1.ldf'

HTH|||thanks! i figured it out. i just changed the localtion from d:\ to c:\ and everything worked.|||damn it! i could restore the db on my local machine but when i tried on the server i get the following error. any idea? thanks.|||What were the options and parameters you were using in your restore?

Also, consider using the RESTORE DATABASE command through SQL. Not everything has to be done through #*(&$^# wizards!

blindman|||Sounds like you're running different editions on your PC and the server.

RESTORE DATABASE is terminating abnormally

Hi DBA there,
I am restoring a bakup from CD with SQL Statement:
RESTORE DATABASE WITE
FROM disk ='e:\wite.bak'
WITH RECOVERY,
MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\wite_mdf.mdf',
MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
Server\MSSQL\log\wite_log.ldf'
i have also use RESTORE FILELISTONLY to ensure the logical name
Unfortunately, the restore is unsuccessful with the result:
Server: Msg 3203, Level 16, State 1, Line 1
Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
more details.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Both physical files wite_data.mdf and wite_log.ldf are in the respective
folders already. On Enterprise manager, the databse WITE status shows
'Loading'.
Please help...
HawleyPermission thing, perhaps? Does the service account have permissions to access the backup file?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"HawleyBeach" <HawleyBeach@.discussions.microsoft.com> wrote in message
news:A07CD252-F19A-4CED-82D7-A5D7185DC181@.microsoft.com...
> Hi DBA there,
> I am restoring a bakup from CD with SQL Statement:
> RESTORE DATABASE WITE
> FROM disk ='e:\wite.bak'
> WITH RECOVERY,
> MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\Data\wite_mdf.mdf',
> MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\log\wite_log.ldf'
> i have also use RESTORE FILELISTONLY to ensure the logical name
> Unfortunately, the restore is unsuccessful with the result:
> Server: Msg 3203, Level 16, State 1, Line 1
> Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
> more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Both physical files wite_data.mdf and wite_log.ldf are in the respective
> folders already. On Enterprise manager, the databse WITE status shows
> 'Loading'.
> Please help...
> Hawley
>|||Copy the back file from CD to hard disk and then try restoring.
Thanks
Hari
"HawleyBeach" <HawleyBeach@.discussions.microsoft.com> wrote in message
news:A07CD252-F19A-4CED-82D7-A5D7185DC181@.microsoft.com...
> Hi DBA there,
> I am restoring a bakup from CD with SQL Statement:
> RESTORE DATABASE WITE
> FROM disk ='e:\wite.bak'
> WITH RECOVERY,
> MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\Data\wite_mdf.mdf',
> MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\log\wite_log.ldf'
> i have also use RESTORE FILELISTONLY to ensure the logical name
> Unfortunately, the restore is unsuccessful with the result:
> Server: Msg 3203, Level 16, State 1, Line 1
> Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
> more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Both physical files wite_data.mdf and wite_log.ldf are in the respective
> folders already. On Enterprise manager, the databse WITE status shows
> 'Loading'.
> Please help...
> Hawley
>

RESTORE DATABASE is terminating abnormally

Hi DBA there,
I am restoring a bakup from CD with SQL Statement:
RESTORE DATABASE WITE
FROM disk ='e:\wite.bak'
WITH RECOVERY,
MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\wite_mdf.mdf',
MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
Server\MSSQL\log\wite_log.ldf'
i have also use RESTORE FILELISTONLY to ensure the logical name
Unfortunately, the restore is unsuccessful with the result:
Server: Msg 3203, Level 16, State 1, Line 1
Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
more details.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Both physical files wite_data.mdf and wite_log.ldf are in the respective
folders already. On Enterprise manager, the databse WITE status shows
'Loading'.
Please help...
Hawley
Permission thing, perhaps? Does the service account have permissions to access the backup file?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"HawleyBeach" <HawleyBeach@.discussions.microsoft.com> wrote in message
news:A07CD252-F19A-4CED-82D7-A5D7185DC181@.microsoft.com...
> Hi DBA there,
> I am restoring a bakup from CD with SQL Statement:
> RESTORE DATABASE WITE
> FROM disk ='e:\wite.bak'
> WITH RECOVERY,
> MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\Data\wite_mdf.mdf',
> MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\log\wite_log.ldf'
> i have also use RESTORE FILELISTONLY to ensure the logical name
> Unfortunately, the restore is unsuccessful with the result:
> Server: Msg 3203, Level 16, State 1, Line 1
> Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
> more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Both physical files wite_data.mdf and wite_log.ldf are in the respective
> folders already. On Enterprise manager, the databse WITE status shows
> 'Loading'.
> Please help...
> Hawley
>
|||Copy the back file from CD to hard disk and then try restoring.
Thanks
Hari
"HawleyBeach" <HawleyBeach@.discussions.microsoft.com> wrote in message
news:A07CD252-F19A-4CED-82D7-A5D7185DC181@.microsoft.com...
> Hi DBA there,
> I am restoring a bakup from CD with SQL Statement:
> RESTORE DATABASE WITE
> FROM disk ='e:\wite.bak'
> WITH RECOVERY,
> MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\Data\wite_mdf.mdf',
> MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\log\wite_log.ldf'
> i have also use RESTORE FILELISTONLY to ensure the logical name
> Unfortunately, the restore is unsuccessful with the result:
> Server: Msg 3203, Level 16, State 1, Line 1
> Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
> more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Both physical files wite_data.mdf and wite_log.ldf are in the respective
> folders already. On Enterprise manager, the databse WITE status shows
> 'Loading'.
> Please help...
> Hawley
>

RESTORE DATABASE is terminating abnormally

Hi DBA there,
I am restoring a bakup from CD with SQL Statement:
RESTORE DATABASE WITE
FROM disk ='e:\wite.bak'
WITH RECOVERY,
MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
Server\MSSQL\Data\wite_mdf.mdf',
MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
Server\MSSQL\log\wite_log.ldf'
i have also use RESTORE FILELISTONLY to ensure the logical name
Unfortunately, the restore is unsuccessful with the result:
Server: Msg 3203, Level 16, State 1, Line 1
Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
more details.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Both physical files wite_data.mdf and wite_log.ldf are in the respective
folders already. On Enterprise manager, the databse WITE status shows
'Loading'.
Please help...
HawleyPermission thing, perhaps? Does the service account have permissions to acce
ss the backup file?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"HawleyBeach" <HawleyBeach@.discussions.microsoft.com> wrote in message
news:A07CD252-F19A-4CED-82D7-A5D7185DC181@.microsoft.com...
> Hi DBA there,
> I am restoring a bakup from CD with SQL Statement:
> RESTORE DATABASE WITE
> FROM disk ='e:\wite.bak'
> WITH RECOVERY,
> MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\Data\wite_mdf.mdf',
> MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\log\wite_log.ldf'
> i have also use RESTORE FILELISTONLY to ensure the logical name
> Unfortunately, the restore is unsuccessful with the result:
> Server: Msg 3203, Level 16, State 1, Line 1
> Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
> more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Both physical files wite_data.mdf and wite_log.ldf are in the respective
> folders already. On Enterprise manager, the databse WITE status shows
> 'Loading'.
> Please help...
> Hawley
>|||Copy the back file from CD to hard disk and then try restoring.
Thanks
Hari
"HawleyBeach" <HawleyBeach@.discussions.microsoft.com> wrote in message
news:A07CD252-F19A-4CED-82D7-A5D7185DC181@.microsoft.com...
> Hi DBA there,
> I am restoring a bakup from CD with SQL Statement:
> RESTORE DATABASE WITE
> FROM disk ='e:\wite.bak'
> WITH RECOVERY,
> MOVE 'wfield_dat' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\Data\wite_mdf.mdf',
> MOVE 'wfield_log' TO 'c:\Program Files\Microsoft SQL
> Server\MSSQL\log\wite_log.ldf'
> i have also use RESTORE FILELISTONLY to ensure the logical name
> Unfortunately, the restore is unsuccessful with the result:
> Server: Msg 3203, Level 16, State 1, Line 1
> Read on 'e:\wite.bak' failed, status = 1. See the SQL Server error log for
> more details.
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> Both physical files wite_data.mdf and wite_log.ldf are in the respective
> folders already. On Enterprise manager, the databse WITE status shows
> 'Loading'.
> Please help...
> Hawley
>sql

Restore database goes to error

Hello everyone,
I'm just restoring database with the ordinary way. But one of my database
reports an error:
"Location: execsql.cpp:230
Expression: exception != se_OK
SPID: 52
Process ID: 572"
SQL Command looks like this:
"USE MASTER RESTORE DATABASE [SourceDB] FROM DISK = 'C:\Backup.bak' WITH
REPLACE
,MOVE 'OldName' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\MDFFileName.mdf'
,MOVE 'OldName_log' TO 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\MDFFileName_log.LDF'"
Any ideas?
Ilia
Hello,
Is this SQL 2000? Can you try restoring the database into a different SQL
Server machine and try if it is working. Just see the size of the database
also. MSDE can support
only a max of 2 GB MDF size.
Thanks
Hari
"ilia" <ilia@.discussions.microsoft.com> wrote in message
news:70D680CF-C9B9-44BA-BC39-93C2724FEBB7@.microsoft.com...
> Hello everyone,
> I'm just restoring database with the ordinary way. But one of my database
> reports an error:
> "Location: execsql.cpp:230
> Expression: exception != se_OK
> SPID: 52
> Process ID: 572"
> SQL Command looks like this:
> "USE MASTER RESTORE DATABASE [SourceDB] FROM DISK = 'C:\Backup.bak' WITH
> REPLACE
> ,MOVE 'OldName' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\MDFFileName.mdf'
> ,MOVE 'OldName_log' TO 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\MDFFileName_log.LDF'"
> Any ideas?
> Ilia

restore database from SQL 2000 to SQL 7.0

The Microsoft Knowledge has many articles on restoring a
database from SQL Server 7.0 to SQL Server 2000, but I
need to do the reverse. I know the process involving
Enterprise Manager and the .BAK file, but it doesn't seem
to work. Are the .BAK files created in SQL Server 2000
compatible with SQL Server 7.0? I have a hunch that
either the character set, sort order, or Unicode collation
are different among the two versions.To my knowledge you can not restore nor attach a 2000 database to a 7.0
server, you might need to use DTS.
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Kyle" <kmitchell@.lmc-ny.com> wrote in message
news:33c501c36db7$9e09a1e0$7d02280a@.phx.gbl...
> The Microsoft Knowledge has many articles on restoring a
> database from SQL Server 7.0 to SQL Server 2000, but I
> need to do the reverse. I know the process involving
> Enterprise Manager and the .BAK file, but it doesn't seem
> to work. Are the .BAK files created in SQL Server 2000
> compatible with SQL Server 7.0? I have a hunch that
> either the character set, sort order, or Unicode collation
> are different among the two versions.

Restore database creates <null>

Hi - I am using sql 2000 - and Enterprise Manager.
When restoring a backup, some ntext (4000) fields are being left as
<null> although there is clearly some text in the original database
fields.
I've been supplied a .bak file of a live database, in order to use it
locally to do some reporting.
I used Enterprise Manager/All Tasks/Restore Database...
1) Created a database
2) Ent-Mgr/Right click over new database (1), Restore Database/General
Tab - restore as database set to my new database (1)
3) Clicked From Device, then Select Devices
4) Clicked Add, then in the Filename field, navigated to the .bak file
on my drive
5) Only restore from media... is unchecked - clicked ok
6) On the Restore Database/Options Tab, Force restore over existing
database is checked, Leave database operational is selected
7) clicked ok, and the database was restored to my new database (1)
When I checked the field, which should contain some text, some records
do, and some just contain <Null> - I have no access to the live server.
Is it likely this is being caused by some other flag I have not
checked/unchecked in Enterprise Manager, or is there something else
anyone can suggest?
Thanks for your help,
Mark
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!A restored database is exactly like the original. The only differences are
(optionally) the database and file names.
If the restored data is not as expected, check to see if the backup file
contains multiple backup sets. You can do this by clicking the 'View
Contents' button on the EM restore dialog. Unless specified otherwise, only
the first (oldest) backup is restored. There is no need to create the
database beforehand because RESTORE will create the database during the
restore process.

> When I checked the field, which should contain some text, some records
> do, and some just contain <Null> - I have no access to the live server.
How can you say for certain that the data is not NULL in the source if you
have no access to the live server?
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <anonymous@.devdex.com> wrote in message
news:eFEymhkSEHA.1168@.TK2MSFTNGP11.phx.gbl...
> Hi - I am using sql 2000 - and Enterprise Manager.
> When restoring a backup, some ntext (4000) fields are being left as
> <null> although there is clearly some text in the original database
> fields.
> I've been supplied a .bak file of a live database, in order to use it
> locally to do some reporting.
> I used Enterprise Manager/All Tasks/Restore Database...
> 1) Created a database
> 2) Ent-Mgr/Right click over new database (1), Restore Database/General
> Tab - restore as database set to my new database (1)
> 3) Clicked From Device, then Select Devices
> 4) Clicked Add, then in the Filename field, navigated to the .bak file
> on my drive
> 5) Only restore from media... is unchecked - clicked ok
> 6) On the Restore Database/Options Tab, Force restore over existing
> database is checked, Leave database operational is selected
> 7) clicked ok, and the database was restored to my new database (1)
> When I checked the field, which should contain some text, some records
> do, and some just contain <Null> - I have no access to the live server.
> Is it likely this is being caused by some other flag I have not
> checked/unchecked in Enterprise Manager, or is there something else
> anyone can suggest?
> Thanks for your help,
> Mark
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Hi Dan - thanks for the pointers - I'll try those when I get back on
Monday.
I know the live server has data, as I can query specific tables and
fields through a web interface.
Cheers, Mark
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||Hi - there is only one backup showing when I check View Contents.
Is there any other reason this may have failed? (different settings on
the install of SQL Server etc?)
Thanks, Mark
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!|||I can't really think of anything that would cause this, assuming the backup
date is as expected. A database restore is all-or-nothing so the databases
should be in sync after the restore.
Have you tried issuing the same queries against both databases via Query
Analyzer? If this yields different results, you might try another
backup/restore.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <anonymous@.devdex.com> wrote in message
news:%23BBodLGTEHA.3872@.TK2MSFTNGP10.phx.gbl...
> Hi - there is only one backup showing when I check View Contents.
> Is there any other reason this may have failed? (different settings on
> the install of SQL Server etc?)
> Thanks, Mark
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!sql

Restore database creates <null>

Hi - I am using sql 2000 - and Enterprise Manager.
When restoring a backup, some ntext (4000) fields are being left as
<null> although there is clearly some text in the original database
fields.
I've been supplied a .bak file of a live database, in order to use it
locally to do some reporting.
I used Enterprise Manager/All Tasks/Restore Database...
1) Created a database
2) Ent-Mgr/Right click over new database (1), Restore Database/General
Tab - restore as database set to my new database (1)
3) Clicked From Device, then Select Devices
4) Clicked Add, then in the Filename field, navigated to the .bak file
on my drive
5) Only restore from media... is unchecked - clicked ok
6) On the Restore Database/Options Tab, Force restore over existing
database is checked, Leave database operational is selected
7) clicked ok, and the database was restored to my new database (1)
When I checked the field, which should contain some text, some records
do, and some just contain <Null> - I have no access to the live server.
Is it likely this is being caused by some other flag I have not
checked/unchecked in Enterprise Manager, or is there something else
anyone can suggest?
Thanks for your help,
Mark
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
A restored database is exactly like the original. The only differences are
(optionally) the database and file names.
If the restored data is not as expected, check to see if the backup file
contains multiple backup sets. You can do this by clicking the 'View
Contents' button on the EM restore dialog. Unless specified otherwise, only
the first (oldest) backup is restored. There is no need to create the
database beforehand because RESTORE will create the database during the
restore process.

> When I checked the field, which should contain some text, some records
> do, and some just contain <Null> - I have no access to the live server.
How can you say for certain that the data is not NULL in the source if you
have no access to the live server?
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <anonymous@.devdex.com> wrote in message
news:eFEymhkSEHA.1168@.TK2MSFTNGP11.phx.gbl...
> Hi - I am using sql 2000 - and Enterprise Manager.
> When restoring a backup, some ntext (4000) fields are being left as
> <null> although there is clearly some text in the original database
> fields.
> I've been supplied a .bak file of a live database, in order to use it
> locally to do some reporting.
> I used Enterprise Manager/All Tasks/Restore Database...
> 1) Created a database
> 2) Ent-Mgr/Right click over new database (1), Restore Database/General
> Tab - restore as database set to my new database (1)
> 3) Clicked From Device, then Select Devices
> 4) Clicked Add, then in the Filename field, navigated to the .bak file
> on my drive
> 5) Only restore from media... is unchecked - clicked ok
> 6) On the Restore Database/Options Tab, Force restore over existing
> database is checked, Leave database operational is selected
> 7) clicked ok, and the database was restored to my new database (1)
> When I checked the field, which should contain some text, some records
> do, and some just contain <Null> - I have no access to the live server.
> Is it likely this is being caused by some other flag I have not
> checked/unchecked in Enterprise Manager, or is there something else
> anyone can suggest?
> Thanks for your help,
> Mark
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi Dan - thanks for the pointers - I'll try those when I get back on
Monday.
I know the live server has data, as I can query specific tables and
fields through a web interface.
Cheers, Mark
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||Hi - there is only one backup showing when I check View Contents.
Is there any other reason this may have failed? (different settings on
the install of SQL Server etc?)
Thanks, Mark
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!
|||I can't really think of anything that would cause this, assuming the backup
date is as expected. A database restore is all-or-nothing so the databases
should be in sync after the restore.
Have you tried issuing the same queries against both databases via Query
Analyzer? If this yields different results, you might try another
backup/restore.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <anonymous@.devdex.com> wrote in message
news:%23BBodLGTEHA.3872@.TK2MSFTNGP10.phx.gbl...
> Hi - there is only one backup showing when I check View Contents.
> Is there any other reason this may have failed? (different settings on
> the install of SQL Server etc?)
> Thanks, Mark
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!

Restore database creates <null>

Hi - I am using sql 2000 - and Enterprise Manager.
When restoring a backup, some ntext (4000) fields are being left as
<null> although there is clearly some text in the original database
fields.
I've been supplied a .bak file of a live database, in order to use it
locally to do some reporting.
I used Enterprise Manager/All Tasks/Restore Database...
1) Created a database
2) Ent-Mgr/Right click over new database (1), Restore Database/General
Tab - restore as database set to my new database (1)
3) Clicked From Device, then Select Devices
4) Clicked Add, then in the Filename field, navigated to the .bak file
on my drive
5) Only restore from media... is unchecked - clicked ok
6) On the Restore Database/Options Tab, Force restore over existing
database is checked, Leave database operational is selected
7) clicked ok, and the database was restored to my new database (1)
When I checked the field, which should contain some text, some records
do, and some just contain <Null> - I have no access to the live server.
Is it likely this is being caused by some other flag I have not
checked/unchecked in Enterprise Manager, or is there something else
anyone can suggest?
Thanks for your help,
Mark
*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!A restored database is exactly like the original. The only differences are
(optionally) the database and file names.
If the restored data is not as expected, check to see if the backup file
contains multiple backup sets. You can do this by clicking the 'View
Contents' button on the EM restore dialog. Unless specified otherwise, only
the first (oldest) backup is restored. There is no need to create the
database beforehand because RESTORE will create the database during the
restore process.
> When I checked the field, which should contain some text, some records
> do, and some just contain <Null> - I have no access to the live server.
How can you say for certain that the data is not NULL in the source if you
have no access to the live server?
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mark" <anonymous@.devdex.com> wrote in message
news:eFEymhkSEHA.1168@.TK2MSFTNGP11.phx.gbl...
> Hi - I am using sql 2000 - and Enterprise Manager.
> When restoring a backup, some ntext (4000) fields are being left as
> <null> although there is clearly some text in the original database
> fields.
> I've been supplied a .bak file of a live database, in order to use it
> locally to do some reporting.
> I used Enterprise Manager/All Tasks/Restore Database...
> 1) Created a database
> 2) Ent-Mgr/Right click over new database (1), Restore Database/General
> Tab - restore as database set to my new database (1)
> 3) Clicked From Device, then Select Devices
> 4) Clicked Add, then in the Filename field, navigated to the .bak file
> on my drive
> 5) Only restore from media... is unchecked - clicked ok
> 6) On the Restore Database/Options Tab, Force restore over existing
> database is checked, Leave database operational is selected
> 7) clicked ok, and the database was restored to my new database (1)
> When I checked the field, which should contain some text, some records
> do, and some just contain <Null> - I have no access to the live server.
> Is it likely this is being caused by some other flag I have not
> checked/unchecked in Enterprise Manager, or is there something else
> anyone can suggest?
> Thanks for your help,
> Mark
>
> *** Sent via Devdex http://www.devdex.com ***
> Don't just participate in USENET...get rewarded for it!

restore database bug

Hi,
I'm having some problem with restoring a database from another server.
The problem is that sql server 2000 is telling me at the end of the
restore process, the user is invalid in the database. It is the same
user which stated the restore statement, but on a testserver. the
database is still restored
The sql-account i'm using is a member of dbcreators.
Should the restore be successful and have an valid owner or is this a bug?Perhaps you want to read up on sp_change_users_login within Books Online
http://msdn.microsoft.com/library/d.../>
cz_8qzy.asp
Here are some other articles that you may find helpful:
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://www.support.microsoft.com/?id=274188
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
INF: Disaster Recovery Articles for Microsoft SQL Server
http://www.support.microsoft.com/?id=307775
INF: Moving SQL Server databases to a new location with Detach/Attach
http://www.support.microsoft.com/?id=224071
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
Database Is Moved
http://www.support.microsoft.com/?id=298897
Keith Kratochvil
"Jason" <jasonlewis@.hotmail.com> wrote in message
news:%236FkksI6GHA.1012@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I'm having some problem with restoring a database from another server.
> The problem is that sql server 2000 is telling me at the end of the
> restore process, the user is invalid in the database. It is the same user
> which stated the restore statement, but on a testserver. the database is
> still restored
> The sql-account i'm using is a member of dbcreators.
> Should the restore be successful and have an valid owner or is this a bug?sql