Backup and Restore Databases Through XML in SQL Express 2005

Can we backup to XML file and restore from XML file in SQL Express 2005?

Thanks in advance.

No, you can't.

Best regards,

Eugene Kogan,

Technical Lead,

Microsoft SQL Server Engine

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Any other alternatives other than XML?|||

Please read articles about BACKUP and RESTORE in SQL Server 2005 Books Online. Also, take a look at "Backing Up and Restoring Databases" article.

Best regards,

Eugene Kogan,

Technical Lead,

SQL Server Engine

This posting is provided "AS IS" with no warranties, and confers no rights.

Backup and restore databases In my MSDE

Hi all! How can i backup databases which are running in my MSDE 2000 & then how can i restore them with all the data, Yes i know that their is no visual tool for doing this in MSDE but can we do it with scripts, if Yes then howThe SQL to backup a database in MSDE is:

BACKUP DATABASE { database_name | @.database_name_var }
TO < backup_device > [ ,...n ]
[ WITH
 [ BLOCKSIZE = { blocksize | @.blocksize_variable } ]
 [ [ , ] DESCRIPTION = { 'text' | @.text_variable } ]
 [ [ , ] DIFFERENTIAL ]
 [ [ , ] EXPIREDATE = { date | @.date_var }
 | RETAINDAYS = { days | @.days_var } ]
 [ [ , ] PASSWORD = { password | @.password_variable } ]
 [ [ , ] FORMAT | NOFORMAT ]
 [ [ , ] { INIT | NOINIT } ]
 [ [ , ] MEDIADESCRIPTION = { 'text' | @.text_variable } ]
 [ [ , ] MEDIANAME = { media_name | @.media_name_variable } ]
 [ [ , ] MEDIAPASSWORD = { mediapassword | @.mediapassword_variable } ]
 [ [ , ] NAME = { backup_set_name | @.backup_set_name_var } ]
 [ [ , ] { NOSKIP | SKIP } ]
 [ [ , ] { NOREWIND | REWIND } ]
 [ [ , ] { NOUNLOAD | UNLOAD } ]
 [ [ , ] RESTART ]
 [ [ , ] STATS [ = percentage ] ]
]

and to restore:

RESTORE DATABASE { database_name | @.database_name_var }
[ FROM < backup_device > [ ,...n ] ]
[ WITH
 [ RESTRICTED_USER ]
 [ [ , ] FILE = { file_number | @.file_number } ]
 [ [ , ] PASSWORD = { password | @.password_variable } ]
 [ [ , ] MEDIANAME = { media_name | @.media_name_variable } ]
 [ [ , ] MEDIAPASSWORD = { mediapassword | @.mediapassword_variable } ]
 [ [ , ] MOVE 'logical_file_name' TO 'operating_system_file_name' ]
 [ ,...n ]
 [ [ , ] KEEP_REPLICATION ]
 [ [ , ] { NORECOVERY | RECOVERY | STANDBY = {undo_file_name|@.undo_file_name_var} } ]
 [ [ , ] { NOREWIND | REWIND } ]
 [ [ , ] { NOUNLOAD | UNLOAD } ]
 [ [ , ] REPLACE ]
 [ [ , ] RESTART ]
 [ [ , ] STATS [ = percentage ] ]
]

Things in square brackets are not strictly speaking required.

Backup and restore databases and access rights

Hi,

I am creating a way of working in order to "copy" databases from a master SQL Server 2000 database to the developers local machines.

I want to create a master SQL Server at our office location. Whenever our developers works on site the master is used. To be able to work locally, a backup has been created of the master and is distributed to the developers. On their local machines, they restore the database to be able to develop locally.

I have created a backup on my laptop using on my domain account (not the account that created the database, but I can use it when developing). I moved the backup file to another computer and restored it using my domain account on that computer. I could not see all of the tables, users or stored procedures, only those which type are System, not User. When i log in to the local administrators account I can see them all. When I log back into my domain account I can see all of the tables.

Anyone knows why?

/M

SQL Enterprise Manager doesn't refresh objects very well. You actually have to force it to refresh sometimes by hitting F5 and even that doesn't always work. Something to try in this case is a quick select statement in query analyzer of a table that you know should be there. Typically it will either show the results or give you the error associated with permissions.

It also sounds like it could be db permissions problems. Typically, SEM connects to the local server via the sa login. So when you login as yourself, you are probably connecting to the server as yourself in SEM. Also keep in mind that objects are owned by their creators and unless permissions are specifically granted for other users/roles or the current user is an admin, you won't be able to work with these objects. So if you created objects under one login (such as sa) you may not be able to see them under another login (such as your domain account). sp_changeobjectowner is a way to modify the owner for each object. sp_MScheck_uid_owns_anything will help determine if the user owns anything; just use the id of the user as the only parameter.

Another option would be to grant all permissions to the public role for all objects as they are created. This is not advised because you are not using SQL Security like it should. But roles are a good thing in environments like this, but these take some setup and administration time.

Backup and Restore Databases

Hello,
I'm restoring some databases and when i take a look in the
users that were created on these databases they do not
appear after the restore. I've done this a lot of times
and this problem never happen before.
Best RegardsYou most probably have orphaned users:
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Server
s
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message news:14f4d01c4159d$92c1a6f0$
a301280a@.phx.gbl...
> Hello,
> I'm restoring some databases and when i take a look in the
> users that were created on these databases they do not
> appear after the restore. I've done this a lot of times
> and this problem never happen before.
> Best Regards|||Have you refreshed the user list?
>--Original Message--
>Hello,
>I'm restoring some databases and when i take a look in
the
>users that were created on these databases they do not
>appear after the restore. I've done this a lot of times
>and this problem never happen before.
>Best Regards
>.
>

backup and restore database on different servers

SQL SERVER 2000 (8.0.2039 ) on both servers.
I need to copy a database from one server to another server. I have created
a backup of the database on source server. Moved the backup(.bak file) on the
destination server. When I try to restore the database on destination server,
On the Restore screen... In the option to select the .bak files (Show backups
of database) I can see the backups of existing databases of the destination
server but not the backup I want to restore which was taken on the source
server.
What needs to be done?
--
DB
ontario, canadaDB,
You need to select the "Restore from device" radio button, then add the file
that you want to restore from.
Any server only has backup history for itself. It does not look for files
on disk of any particular pattern, it looks at the history in msdb.
RLF
"db" <db@.discussions.microsoft.com> wrote in message
news:E99E95DC-B68D-4325-9E65-35B6548CA6D1@.microsoft.com...
> SQL SERVER 2000 (8.0.2039 ) on both servers.
> I need to copy a database from one server to another server. I have
> created
> a backup of the database on source server. Moved the backup(.bak file) on
> the
> destination server. When I try to restore the database on destination
> server,
> On the Restore screen... In the option to select the .bak files (Show
> backups
> of database) I can see the backups of existing databases of the
> destination
> server but not the backup I want to restore which was taken on the source
> server.
> What needs to be done?
> --
> DB
> ontario, canada|||Have it backup from a device and specify the file there. Also, your build
of SQL Server 2000 has a known bug. Check out the following build chart and
apply the hotfix:
http://aspfaq.com/SQL2000Builds.asp
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"db" <db@.discussions.microsoft.com> wrote in message
news:E99E95DC-B68D-4325-9E65-35B6548CA6D1@.microsoft.com...
SQL SERVER 2000 (8.0.2039 ) on both servers.
I need to copy a database from one server to another server. I have created
a backup of the database on source server. Moved the backup(.bak file) on
the
destination server. When I try to restore the database on destination
server,
On the Restore screen... In the option to select the .bak files (Show
backups
of database) I can see the backups of existing databases of the destination
server but not the backup I want to restore which was taken on the source
server.
What needs to be done?
--
DB
ontario, canada|||Hi Russel
Under the options
1. Logical file name: I will keep same logical file names.
2. Move to Physical file name: Can I change it and give the path where I
want to install the .mdf and .ldf files on the destination server.
I know this is a silly question but I do not want to test it as working on
production server.
Thanks
DB
ontario, canada
"Russell Fields" wrote:
> DB,
> You need to select the "Restore from device" radio button, then add the file
> that you want to restore from.
> Any server only has backup history for itself. It does not look for files
> on disk of any particular pattern, it looks at the history in msdb.
> RLF
> "db" <db@.discussions.microsoft.com> wrote in message
> news:E99E95DC-B68D-4325-9E65-35B6548CA6D1@.microsoft.com...
> > SQL SERVER 2000 (8.0.2039 ) on both servers.
> > I need to copy a database from one server to another server. I have
> > created
> > a backup of the database on source server. Moved the backup(.bak file) on
> > the
> > destination server. When I try to restore the database on destination
> > server,
> > On the Restore screen... In the option to select the .bak files (Show
> > backups
> > of database) I can see the backups of existing databases of the
> > destination
> > server but not the backup I want to restore which was taken on the source
> > server.
> > What needs to be done?
> > --
> > DB
> > ontario, canada
>
>|||Yep. Often the path on the destination serer is different from the original
server. Just specify whatever path you want.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"db" <db@.discussions.microsoft.com> wrote in message
news:5BAF9FB9-6699-4716-A302-20E39B46ED11@.microsoft.com...
Hi Russel
Under the options
1. Logical file name: I will keep same logical file names.
2. Move to Physical file name: Can I change it and give the path where I
want to install the .mdf and .ldf files on the destination server.
I know this is a silly question but I do not want to test it as working on
production server.
Thanks
DB
ontario, canada
"Russell Fields" wrote:
> DB,
> You need to select the "Restore from device" radio button, then add the
file
> that you want to restore from.
> Any server only has backup history for itself. It does not look for files
> on disk of any particular pattern, it looks at the history in msdb.
> RLF
> "db" <db@.discussions.microsoft.com> wrote in message
> news:E99E95DC-B68D-4325-9E65-35B6548CA6D1@.microsoft.com...
> > SQL SERVER 2000 (8.0.2039 ) on both servers.
> > I need to copy a database from one server to another server. I have
> > created
> > a backup of the database on source server. Moved the backup(.bak file)
on
> > the
> > destination server. When I try to restore the database on destination
> > server,
> > On the Restore screen... In the option to select the .bak files (Show
> > backups
> > of database) I can see the backups of existing databases of the
> > destination
> > server but not the backup I want to restore which was taken on the
source
> > server.
> > What needs to be done?
> > --
> > DB
> > ontario, canada
>
>|||DB,
Yes, you can give it the new paths where you want the .mdf and .ldf files to
reside.
Of course, I recommend always testing new commands on a test server. (I
just tested this on one of my SQL 2000 servers, using both SQL Server
Management Studio 2005 and SQL Server 2000 Enterprise Manager.)
RLF
"db" <db@.discussions.microsoft.com> wrote in message
news:5BAF9FB9-6699-4716-A302-20E39B46ED11@.microsoft.com...
> Hi Russel
> Under the options
> 1. Logical file name: I will keep same logical file names.
> 2. Move to Physical file name: Can I change it and give the path where I
> want to install the .mdf and .ldf files on the destination server.
> I know this is a silly question but I do not want to test it as working on
> production server.
> Thanks
> DB
>
> --
> ontario, canada
>
> "Russell Fields" wrote:
>> DB,
>> You need to select the "Restore from device" radio button, then add the
>> file
>> that you want to restore from.
>> Any server only has backup history for itself. It does not look for
>> files
>> on disk of any particular pattern, it looks at the history in msdb.
>> RLF
>> "db" <db@.discussions.microsoft.com> wrote in message
>> news:E99E95DC-B68D-4325-9E65-35B6548CA6D1@.microsoft.com...
>> > SQL SERVER 2000 (8.0.2039 ) on both servers.
>> > I need to copy a database from one server to another server. I have
>> > created
>> > a backup of the database on source server. Moved the backup(.bak file)
>> > on
>> > the
>> > destination server. When I try to restore the database on destination
>> > server,
>> > On the Restore screen... In the option to select the .bak files (Show
>> > backups
>> > of database) I can see the backups of existing databases of the
>> > destination
>> > server but not the backup I want to restore which was taken on the
>> > source
>> > server.
>> > What needs to be done?
>> > --
>> > DB
>> > ontario, canada
>>

Backup and restore database hourly: how to implement it?

I have two servers, using SQL server 2000.
I was asked for implementing hourly Backup 3 databases in one server
and restore those databases to another server.

Could anyone give me the detailed steps to do that?
Thanks a lot in advance!<danceli@.gmail.comwrote in message
news:1171500668.532022.161870@.l53g2000cwa.googlegr oups.com...

Quote:

Originally Posted by

>I have two servers, using SQL server 2000.
I was asked for implementing hourly Backup 3 databases in one server
and restore those databases to another server.

Google log-shipping.

You really only want to do a ful restore to server B, and then transaction
log backup/restores after that.

Quote:

Originally Posted by

>
Could anyone give me the detailed steps to do that?
Thanks a lot in advance!
>

|||Log shipping is a process that takes transaction logs from a primary
SQL Server and applies them sequentially on a scheduled basis to
another SQL Server.

Does this do same thing for Backup/Restore the database?? Thanks a lot
for any explaination. I do have no idea about that.

Quote:

Originally Posted by

Google log-shipping.
>
You really only want to do a ful restore to server B, and then transaction
logbackup/restores after that.
>
>

|||<danceli@.gmail.comwrote in message
news:1171503793.953050.302190@.q2g2000cwa.googlegro ups.com...

Quote:

Originally Posted by

Log shipping is a process that takes transaction logs from a primary
SQL Server and applies them sequentially on a scheduled basis to
another SQL Server.
>
Does this do same thing for Backup/Restore the database?? Thanks a lot
for any explaination. I do have no idea about that.

Generally you don't want to do a full backup/restore due to the time.

Is there a specific reasony ou want to do a full backup/restore rather than
simply log-shipping?

Quote:

Originally Posted by

>

Quote:

Originally Posted by

>Google log-shipping.
>>
>You really only want to do a ful restore to server B, and then
>transaction
>logbackup/restores after that.
>>
>>

>

|||You mean logshipping could also do backup database and restore the
databases to another server also?

On Feb 14, 7:36 pm, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.comwrote:

Quote:

Originally Posted by

Generally you don't want to do a fullbackup/restore due to the time.
>
Is there a specific reasony ou want to do a fullbackup/restore rather than
simply log-shipping?
>

|||<danceli@.gmail.comwrote in message
news:1171561856.821679.57780@.a75g2000cwd.googlegro ups.com...

Quote:

Originally Posted by

You mean logshipping could also do backup database and restore the
databases to another server also?

Generally you have to do the initial backup/restore yourself.

I've written scripts in the past to do a full backup/restore but that was a
specialized case that I replaced with a log-shipping script the first chance
I got.

I'm still unclear why you want to go the full backup/restore route rather
than using log-shipping.

Quote:

Originally Posted by

>
>
On Feb 14, 7:36 pm, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.comwrote:
>

Quote:

Originally Posted by

>Generally you don't want to do a fullbackup/restore due to the time.
>>
>Is there a specific reasony ou want to do a fullbackup/restore rather
>than
>simply log-shipping?
>>

>

|||Actually we need replicate 3 databases from server A to server B. But
no idea why replication does not work fine.

So, my boss asked me to do hourly full backup/restore to server B,
which is kind of relication.

Now I still can schedule a job for hourly full backup on server A, but
i have no idea how to schedule a job for hourly full restore dbs to
server B.

How to make those hourly .Bak files in server A to server B, and then
do restore in server B??

BTW, thank you so much to keep helping me out!!

On Feb 15, 10:48 am, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.comwrote:

Quote:

Originally Posted by

>
Generally you have to do the initialbackup/restore yourself.
>
I've written scripts in the past to do a fullbackup/restore but that was a
specialized case that I replaced with a log-shipping script the first chance
I got.
>
I'm still unclear why you want to go the fullbackup/restore route rather
than using log-shipping.

|||
--
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com

<danceli@.gmail.comwrote in message
news:1171570480.195547.91540@.v33g2000cwv.googlegro ups.com...

Quote:

Originally Posted by

Actually we need replicate 3 databases from server A to server B. But
no idea why replication does not work fine.
>

I'd focus on fixing that.

Quote:

Originally Posted by

So, my boss asked me to do hourly full backup/restore to server B,
which is kind of relication.

Questions to ask then:
1) What do you do on Server B while the restore is taking place?
2) What do you do if the backup/restore cycle takes more than an hour?

With log-shipping at least you can put the databases on server B into
"read-only" mode between log restores.

Quote:

Originally Posted by

>
Now I still can schedule a job for hourly full backup on server A, but
i have no idea how to schedule a job for hourly full restore dbs to
server B.
>
How to make those hourly .Bak files in server A to server B, and then
do restore in server B??

What I basically did was create a job on Server A that performed the backup
and then called a job on ServerB to start the restore. (ServerB would look
to the MSDB on ServerA to find the most recentlly performed backup and
location and restore that.)

Quote:

Originally Posted by

>
BTW, thank you so much to keep helping me out!!
>
>
On Feb 15, 10:48 am, "Greg D. Moore \(Strider\)"
<mooregr_deletet...@.greenms.comwrote:

Quote:

Originally Posted by

>>
>Generally you have to do the initialbackup/restore yourself.
>>
>I've written scripts in the past to do a fullbackup/restore but that was
>a
>specialized case that I replaced with a log-shipping script the first
>chance
>I got.
>>
>I'm still unclear why you want to go the fullbackup/restore route rather
>than using log-shipping.

>
>
>

|||(danceli@.gmail.com) writes:

Quote:

Originally Posted by

Now I still can schedule a job for hourly full backup on server A, but
i have no idea how to schedule a job for hourly full restore dbs to
server B.

ALTER DATBASE db SET SINGLE_USER WITH ROLLBACK IMMEDIATE
RESTORE DATAHASE dh FROM DISK='locationofbackup'
ALTER DATABASE db SET MULTI_USER

Then use Enterprise Manager or Mgmt Studio to create a job, with this
as the job step and set up a schedule.

Of course, log shipping would be better, but if the databases are small,
less then 1 GB, that's probably not worth the hassle.

--
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|||The backup file is located in server A.
how should do restore in Server B to catching backup file from serer
A??

Need I copy the backup.bak file from server A to Server B, then
schedule job to restore at server B?
How to set it automatically?

On Feb 15, 2:47 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:

Quote:

Originally Posted by

Quote:

Originally Posted by

Now I still can schedule a job for hourly full backup on server A, but
i have no idea how to schedule a job for hourly full restore dbs to
server B.

>
ALTER DATBASE db SET SINGLE_USER WITH ROLLBACK IMMEDIATE
RESTORE DATAHASE dh FROM DISK='locationofbackup'
ALTER DATABASE db SET MULTI_USER
>
Then use Enterprise Manager or Mgmt Studio to create a job, with this
as the job step and set up a schedule.

|||<danceli@.gmail.comwrote in message
news:1171584368.655858.325050@.p10g2000cwp.googlegr oups.com...

Quote:

Originally Posted by

The backup file is located in server A.
how should do restore in Server B to catching backup file from serer
A??
>

Use UNCs to refer to the location of the backup.

I'm assuming you're NOT backing up the file to the same local disk on
ServerA.

Quote:

Originally Posted by

Need I copy the backup.bak file from server A to Server B, then
schedule job to restore at server B?
How to set it automatically?
>
>
On Feb 15, 2:47 pm, Erland Sommarskog <esq...@.sommarskog.sewrote:
>

Quote:

Originally Posted by

Quote:

Originally Posted by

Now I still can schedule a job for hourly full backup on server A, but
i have no idea how to schedule a job for hourly full restore dbs to
server B.

>>
>ALTER DATBASE db SET SINGLE_USER WITH ROLLBACK IMMEDIATE
>RESTORE DATAHASE dh FROM DISK='locationofbackup'
>ALTER DATABASE db SET MULTI_USER
>>
>Then use Enterprise Manager or Mgmt Studio to create a job, with this
>as the job step and set up a schedule.

>

|||Greg D. Moore (Strider) wrote:

Quote:

Originally Posted by

Quote:

Originally Posted by

>The backup file is located in server A.
>how should do restore in Server B to catching backup file from serer
>A??
>>

>
Use UNCs to refer to the location of the backup.
>

If the servers' drives are not accessible via UNC, FTP can be scripted
and works pretty well. You can create a batch file to compress the
backup and ftp it to the remote server. Your remote server can then
'look' for new backups at a certain interval, uncompress it and restore
it. I believe you could do all of this in batch files if desired or in
SQL jobs. Use whatever you are most familiar with.|||Greg D. Moore (Strider) wrote:

Quote:

Originally Posted by

I'm still unclear why you want to go the full backup/restore route rather
than using log-shipping.

Greg,

Log shipping requires Enterprise Edition, right?

Jonathan|||
--
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com

"Jonathan Roberts" <gremln007@.diynics.comwrote in message
news:YabBh.12926$JF.1221@.newsfe21.lga...

Quote:

Originally Posted by

Greg D. Moore (Strider) wrote:

Quote:

Originally Posted by

>I'm still unclear why you want to go the full backup/restore route rather
>than using log-shipping.

>
Greg,
>
Log shipping requires Enterprise Edition, right?

If you want to use the built-in scripts yes.

But there's nothing to prevent you from rolling your own. Which I've done
in the past.

Quote:

Originally Posted by

>
Jonathan

Backup and restore database from local drive to hosting server

Hello all,

I'm new to SQL server and I've just seutp a website using the new Visual Web Developer and SQL 2005 Express. I've got my website out on the hosting site server but I need to copy my database file to the hosting site's sql 2005 server. I asked my provider how to do this and they advised to use SQL Server Mgmt Stuido and to perform a backup of my local database file and then do a restore to their server. First they said to create a database on their server using a web based control panel provided with the site controls (this would be a temporary database overwritten by my local copy on the restore - I'm assuming). Then I could do my backup and restore.

I've not been successful doing this. I can connect to their server and my temporary database and can also backup my local database. I cannot, however see how to restore my backup copy to the remote site's sql server. When I choose to restore a database on the remote site, I am only provided with a file browser with folders the SQL Server instance can see. These obviously are not any of my local files so I can't use my local backup. I can't backup my file directly to the server because of the same issue, my local SQL instance can only see my local files, not the remote site directories.

I am probably overlooking something obvious but I really could use any input offered.

Thanks in advance for any help.

Regards,
Scott

Hi all:

Update to this issue, I finally resolved it. I just decided to recreate the database manually on the server using scripts. I connected in SQL Server Mgmt Studio to my remote db server and ran all the scripts I created from my local database. This took a while but I was able to finally get it finished and it now works great.

Backup and restore database between computers

What is the way(s) to backup a database from a Server and restore it to
another?
Thanks for replying...
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200608/1One way is to do a backup in SQL, then restore it on another server -
however, you have to worry about whether the servers are running the same
version of SQL. If not you need to be aware of what the differences are
and what to do about them.
You can detach, copy the db and attach it on the new server - again see
above about version diffrences.
pedestrian via droptable.com wrote:

> What is the way(s) to backup a database from a Server and restore it to
> another?
> Thanks for replying...
>
Brett I. Holcomb
brettholcomb@.R777bellsouth.net
Remove R777 to email|||Thanks for the answer, Brett.
Brett I. Holcomb wrote:
>One way is to do a backup in SQL, then restore it on another server ...
Message posted via http://www.droptable.com

Backup and restore database between computers

What is the way(s) to backup a database from a Server and restore it to
another?
Thanks for replying...
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200608/1One way is to do a backup in SQL, then restore it on another server -
however, you have to worry about whether the servers are running the same
version of SQL. If not you need to be aware of what the differences are
and what to do about them.
You can detach, copy the db and attach it on the new server - again see
above about version diffrences.
pedestrian via SQLMonster.com wrote:
> What is the way(s) to backup a database from a Server and restore it to
> another?
> Thanks for replying...
>
--
Brett I. Holcomb
brettholcomb@.R777bellsouth.net
Remove R777 to email|||Thanks for the answer, Brett.
Brett I. Holcomb wrote:
>One way is to do a backup in SQL, then restore it on another server ...
--
Message posted via http://www.sqlmonster.com

Backup and Restore best practices

I have recently been asked to produce a document recommending backup and
restore best practices in a new company.
They current use a very large backup script in a stored procedure (with
parameters) which is used across all servers that automates things to a large
degree. Whilst I can see the advantages of this I can see more bad than good.
This script is obviously scheduled within a job, this has many steps of
other operations.
Does anyone have any good references for the best backup procedures/ setup
that will help me come to some kind of decision?
e.g. For instance setup of the jobs/ setps, storage locations of files,
frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
sqlBackupDevices (or not), alerting etc etc.
I have many many books that I can look at, so I'm not looking for
information on how to do stuff, only Best Practice (or Functional)
recommendations
Thanks in advance.
Best Regards,
Mark Broadbent
Mark
http://vyaskn.tripod.com/sql_server_...ices.htm#Step1
--administaiting best practices
"Mark Broadbent" <nospam@.nospam.com> wrote in message
news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>I have recently been asked to produce a document recommending backup and
> restore best practices in a new company.
> They current use a very large backup script in a stored procedure (with
> parameters) which is used across all servers that automates things to a
> large
> degree. Whilst I can see the advantages of this I can see more bad than
> good.
> This script is obviously scheduled within a job, this has many steps of
> other operations.
> Does anyone have any good references for the best backup procedures/ setup
> that will help me come to some kind of decision?
> e.g. For instance setup of the jobs/ setps, storage locations of files,
> frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
> sqlBackupDevices (or not), alerting etc etc.
> I have many many books that I can look at, so I'm not looking for
> information on how to do stuff, only Best Practice (or Functional)
> recommendations
> Thanks in advance.
> --
> Best Regards,
> Mark Broadbent
|||Had already found this URI, but am hoping for more detailed information (or
Microsoft recommend docs/ links).
Thanks anyway for your input.
Best Regards,
Mark Broadbent
"Uri Dimant" wrote:

> Mark
> http://vyaskn.tripod.com/sql_server_...ices.htm#Step1
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>
>
|||The Operations Guide has some information as well. Not just
the backup and restore section but the Administrative tasks
and other areas in the section on Systems Administration:
http://www.microsoft.com/technet/pro...n/sqlops4.mspx
-Sue
On Wed, 27 Sep 2006 07:33:02 -0700, Mark Broadbent
<nospam@.nospam.com> wrote:

>Had already found this URI, but am hoping for more detailed information (or
>Microsoft recommend docs/ links).
>Thanks anyway for your input.

Backup and Restore best practices

I have recently been asked to produce a document recommending backup and
restore best practices in a new company.
They current use a very large backup script in a stored procedure (with
parameters) which is used across all servers that automates things to a large
degree. Whilst I can see the advantages of this I can see more bad than good.
This script is obviously scheduled within a job, this has many steps of
other operations.
Does anyone have any good references for the best backup procedures/ setup
that will help me come to some kind of decision?
e.g. For instance setup of the jobs/ setps, storage locations of files,
frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
sqlBackupDevices (or not), alerting etc etc.
I have many many books that I can look at, so I'm not looking for
information on how to do stuff, only Best Practice (or Functional)
recommendations
Thanks in advance.
--
Best Regards,
Mark BroadbentMark
http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1
--administaiting best practices
"Mark Broadbent" <nospam@.nospam.com> wrote in message
news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>I have recently been asked to produce a document recommending backup and
> restore best practices in a new company.
> They current use a very large backup script in a stored procedure (with
> parameters) which is used across all servers that automates things to a
> large
> degree. Whilst I can see the advantages of this I can see more bad than
> good.
> This script is obviously scheduled within a job, this has many steps of
> other operations.
> Does anyone have any good references for the best backup procedures/ setup
> that will help me come to some kind of decision?
> e.g. For instance setup of the jobs/ setps, storage locations of files,
> frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
> sqlBackupDevices (or not), alerting etc etc.
> I have many many books that I can look at, so I'm not looking for
> information on how to do stuff, only Best Practice (or Functional)
> recommendations
> Thanks in advance.
> --
> Best Regards,
> Mark Broadbent|||Had already found this URI, but am hoping for more detailed information (or
Microsoft recommend docs/ links).
Thanks anyway for your input.
--
Best Regards,
Mark Broadbent
"Uri Dimant" wrote:
> Mark
> http://vyaskn.tripod.com/sql_server_administration_best_practices.htm#Step1
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
> >I have recently been asked to produce a document recommending backup and
> > restore best practices in a new company.
> >
> > They current use a very large backup script in a stored procedure (with
> > parameters) which is used across all servers that automates things to a
> > large
> > degree. Whilst I can see the advantages of this I can see more bad than
> > good.
> > This script is obviously scheduled within a job, this has many steps of
> > other operations.
> >
> > Does anyone have any good references for the best backup procedures/ setup
> > that will help me come to some kind of decision?
> >
> > e.g. For instance setup of the jobs/ setps, storage locations of files,
> > frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
> > sqlBackupDevices (or not), alerting etc etc.
> >
> > I have many many books that I can look at, so I'm not looking for
> > information on how to do stuff, only Best Practice (or Functional)
> > recommendations
> >
> > Thanks in advance.
> > --
> > Best Regards,
> >
> > Mark Broadbent
>
>|||The Operations Guide has some information as well. Not just
the backup and restore section but the Administrative tasks
and other areas in the section on Systems Administration:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops4.mspx
-Sue
On Wed, 27 Sep 2006 07:33:02 -0700, Mark Broadbent
<nospam@.nospam.com> wrote:
>Had already found this URI, but am hoping for more detailed information (or
>Microsoft recommend docs/ links).
>Thanks anyway for your input.

Backup and Restore best practices

I have recently been asked to produce a document recommending backup and
restore best practices in a new company.
They current use a very large backup script in a stored procedure (with
parameters) which is used across all servers that automates things to a larg
e
degree. Whilst I can see the advantages of this I can see more bad than good
.
This script is obviously scheduled within a job, this has many steps of
other operations.
Does anyone have any good references for the best backup procedures/ setup
that will help me come to some kind of decision?
e.g. For instance setup of the jobs/ setps, storage locations of files,
frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
sqlBackupDevices (or not), alerting etc etc.
I have many many books that I can look at, so I'm not looking for
information on how to do stuff, only Best Practice (or Functional)
recommendations
Thanks in advance.
--
Best Regards,
Mark BroadbentMark
http://vyaskn.tripod.com/ sql_serve...r />
.htm#Step1
--administaiting best practices
"Mark Broadbent" <nospam@.nospam.com> wrote in message
news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>I have recently been asked to produce a document recommending backup and
> restore best practices in a new company.
> They current use a very large backup script in a stored procedure (with
> parameters) which is used across all servers that automates things to a
> large
> degree. Whilst I can see the advantages of this I can see more bad than
> good.
> This script is obviously scheduled within a job, this has many steps of
> other operations.
> Does anyone have any good references for the best backup procedures/ setup
> that will help me come to some kind of decision?
> e.g. For instance setup of the jobs/ setps, storage locations of files,
> frequency, types (e.g. Full, Diff, Tran), Recovery models, usage of
> sqlBackupDevices (or not), alerting etc etc.
> I have many many books that I can look at, so I'm not looking for
> information on how to do stuff, only Best Practice (or Functional)
> recommendations
> Thanks in advance.
> --
> Best Regards,
> Mark Broadbent|||Had already found this URI, but am hoping for more detailed information (or
Microsoft recommend docs/ links).
Thanks anyway for your input.
--
Best Regards,
Mark Broadbent
"Uri Dimant" wrote:

> Mark
> [url]http://vyaskn.tripod.com/ sql_server_administration_best_practices
.htm#Step1[/url
]
> --administaiting best practices
>
>
>
> "Mark Broadbent" <nospam@.nospam.com> wrote in message
> news:2FEF6FE9-DA88-41C4-B640-C42AB1733FA2@.microsoft.com...
>
>|||The Operations Guide has some information as well. Not just
the backup and restore section but the Administrative tasks
and other areas in the section on Systems Administration:
http://www.microsoft.com/technet/pr...in/sqlops4.mspx
-Sue
On Wed, 27 Sep 2006 07:33:02 -0700, Mark Broadbent
<nospam@.nospam.com> wrote:

>Had already found this URI, but am hoping for more detailed information (or
>Microsoft recommend docs/ links).
>Thanks anyway for your input.

Backup and Restore Anomaly

SQL Server 2000 SP4 build 2187
Not sure what is happening with SQL Server backup Internals, I am hoping you
can answer.
A scheduled job backups up database named "Wells" to a device which points
to a physical file as step 1. Same schedule job, step 2, then restores to
database WELLSCopy. The WELLSCopy database has always existed. This has been
working for a very long time. Now, its generating the following error.
Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
Database' :
Began Executing 2006-10-19 00:59:34
Msg 3141, Sev 16: The database to be restored was named 'Wells'.
Reissue the statement using the WITH REPLACE option to overwrite the
'WELLScopy'
database. [SQLSTATE 42000]
Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE
42000]
Here is the backup command and restore command.
BACKUP DATABASE [Wells] TO Dbackup_WELLS
WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
restore database CHARITYDBCOPY
from dbackup_charitydb
with
move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
I tried to duplicate this issue in our test environment and it restored
successfully every time. I did manage to break it by creating a new database
with a totally different name then try to restore over it and received the
error message.
BOL says it performs a safety check if the REPLACE options is not used. If
so, why has the restore work for a very long time and now decide to break.
Also, why is it allowing me to restore successfully in test without using th
e
REPLACE option.
I am so confused...
BOL...
When the REPLACE option is not specified, a safety check occurs (which
prevents overwriting a different database by accident). The safety check
ensures that the RESTORE DATABASE statement will not restore the database to
the current server if:
The database named in the RESTORE statement already exists on the current
server, and
The database name is different from the database name recorded in the backup
set.I applogize, I pasted my test restore code. Here is the correct version
RESTORE DATABASE WELLScopy
FROM Dbackup_wells
with
MOVE 'Wells_Data' TO 'e:\data\mssql\data\WELLScopy_Data.MDF',
MOVE 'WELLS_Log' TO 'e:\data\mssql\data\WELLScopy_Log.LDF'
go
"FredG" wrote:

> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping y
ou
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has be
en
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTAT
E 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new databa
se
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using
the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database
to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the back
up
> set.
>|||A guess is that the source database has grown, so the backup need say 10GB f
or one of the database
files, but the existing database file only has, say, 8GB for that file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping y
ou
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has be
en
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTAT
E 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new databa
se
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using
the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database
to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the back
up
> set.
>|||Hi Tibor,
Thanks for the repsonse. We finally found the actual problem. Someone
restored the copy data outside of the normal job. Once we dropped and
recreated the job functioned as normal. Very strange behavior I must add.
"Tibor Karaszi" wrote:

> A guess is that the source database has grown, so the backup need say 10GB
for one of the database
> files, but the existing database file only has, say, 8GB for that file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
>

Backup and Restore Anomaly

SQL Server 2000 SP4 build 2187
Not sure what is happening with SQL Server backup Internals, I am hoping you
can answer.
A scheduled job backups up database named "Wells" to a device which points
to a physical file as step 1. Same schedule job, step 2, then restores to
database WELLSCopy. The WELLSCopy database has always existed. This has been
working for a very long time. Now, its generating the following error.
Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
Database' :
Began Executing 2006-10-19 00:59:34
Msg 3141, Sev 16: The database to be restored was named 'Wells'.
Reissue the statement using the WITH REPLACE option to overwrite the
'WELLScopy'
database. [SQLSTATE 42000]
Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
Here is the backup command and restore command.
BACKUP DATABASE [Wells] TO Dbackup_WELLS
WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
restore database CHARITYDBCOPY
from dbackup_charitydb
with
move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
I tried to duplicate this issue in our test environment and it restored
successfully every time. I did manage to break it by creating a new database
with a totally different name then try to restore over it and received the
error message.
BOL says it performs a safety check if the REPLACE options is not used. If
so, why has the restore work for a very long time and now decide to break.
Also, why is it allowing me to restore successfully in test without using the
REPLACE option.
I am so confused...
BOL...
When the REPLACE option is not specified, a safety check occurs (which
prevents overwriting a different database by accident). The safety check
ensures that the RESTORE DATABASE statement will not restore the database to
the current server if:
The database named in the RESTORE statement already exists on the current
server, and
The database name is different from the database name recorded in the backup
set.I applogize, I pasted my test restore code. Here is the correct version
RESTORE DATABASE WELLScopy
FROM Dbackup_wells
with
MOVE 'Wells_Data' TO 'e:\data\mssql\data\WELLScopy_Data.MDF',
MOVE 'WELLS_Log' TO 'e:\data\mssql\data\WELLScopy_Log.LDF'
go
"FredG" wrote:
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>|||A guess is that the source database has grown, so the backup need say 10GB for one of the database
files, but the existing database file only has, say, 8GB for that file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>|||Hi Tibor,
Thanks for the repsonse. We finally found the actual problem. Someone
restored the copy data outside of the normal job. Once we dropped and
recreated the job functioned as normal. Very strange behavior I must add.
"Tibor Karaszi" wrote:
> A guess is that the source database has grown, so the backup need say 10GB for one of the database
> files, but the existing database file only has, say, 8GB for that file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> > SQL Server 2000 SP4 build 2187
> >
> > Not sure what is happening with SQL Server backup Internals, I am hoping you
> > can answer.
> >
> > A scheduled job backups up database named "Wells" to a device which points
> > to a physical file as step 1. Same schedule job, step 2, then restores to
> > database WELLSCopy. The WELLSCopy database has always existed. This has been
> > working for a very long time. Now, its generating the following error.
> >
> > Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> > Database' :
> > Began Executing 2006-10-19 00:59:34
> > Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> > Reissue the statement using the WITH REPLACE option to overwrite the
> > 'WELLScopy'
> > database. [SQLSTATE 42000]
> > Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
> >
> >
> > Here is the backup command and restore command.
> > BACKUP DATABASE [Wells] TO Dbackup_WELLS
> > WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
> >
> >
> > restore database CHARITYDBCOPY
> > from dbackup_charitydb
> > with
> > move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> > move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
> >
> >
> > I tried to duplicate this issue in our test environment and it restored
> > successfully every time. I did manage to break it by creating a new database
> > with a totally different name then try to restore over it and received the
> > error message.
> >
> > BOL says it performs a safety check if the REPLACE options is not used. If
> > so, why has the restore work for a very long time and now decide to break.
> > Also, why is it allowing me to restore successfully in test without using the
> > REPLACE option.
> >
> > I am so confused...
> >
> > BOL...
> > When the REPLACE option is not specified, a safety check occurs (which
> > prevents overwriting a different database by accident). The safety check
> > ensures that the RESTORE DATABASE statement will not restore the database to
> > the current server if:
> > The database named in the RESTORE statement already exists on the current
> > server, and
> > The database name is different from the database name recorded in the backup
> > set.
> >
>

Backup and Restore Anomaly

SQL Server 2000 SP4 build 2187
Not sure what is happening with SQL Server backup Internals, I am hoping you
can answer.
A scheduled job backups up database named "Wells" to a device which points
to a physical file as step 1. Same schedule job, step 2, then restores to
database WELLSCopy. The WELLSCopy database has always existed. This has been
working for a very long time. Now, its generating the following error.
Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
Database' :
Began Executing 2006-10-19 00:59:34
Msg 3141, Sev 16: The database to be restored was named 'Wells'.
Reissue the statement using the WITH REPLACE option to overwrite the
'WELLScopy'
database. [SQLSTATE 42000]
Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
Here is the backup command and restore command.
BACKUP DATABASE [Wells] TO Dbackup_WELLS
WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
restore database CHARITYDBCOPY
from dbackup_charitydb
with
move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
I tried to duplicate this issue in our test environment and it restored
successfully every time. I did manage to break it by creating a new database
with a totally different name then try to restore over it and received the
error message.
BOL says it performs a safety check if the REPLACE options is not used. If
so, why has the restore work for a very long time and now decide to break.
Also, why is it allowing me to restore successfully in test without using the
REPLACE option.
I am so confused...
BOL...
When the REPLACE option is not specified, a safety check occurs (which
prevents overwriting a different database by accident). The safety check
ensures that the RESTORE DATABASE statement will not restore the database to
the current server if:
The database named in the RESTORE statement already exists on the current
server, and
The database name is different from the database name recorded in the backup
set.
I applogize, I pasted my test restore code. Here is the correct version
RESTORE DATABASE WELLScopy
FROM Dbackup_wells
with
MOVE 'Wells_Data' TO 'e:\data\mssql\data\WELLScopy_Data.MDF',
MOVE 'WELLS_Log' TO 'e:\data\mssql\data\WELLScopy_Log.LDF'
go
"FredG" wrote:

> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>
|||A guess is that the source database has grown, so the backup need say 10GB for one of the database
files, but the existing database file only has, say, 8GB for that file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"FredG" <FredG@.discussions.microsoft.com> wrote in message
news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
> SQL Server 2000 SP4 build 2187
> Not sure what is happening with SQL Server backup Internals, I am hoping you
> can answer.
> A scheduled job backups up database named "Wells" to a device which points
> to a physical file as step 1. Same schedule job, step 2, then restores to
> database WELLSCopy. The WELLSCopy database has always existed. This has been
> working for a very long time. Now, its generating the following error.
> Job '0405 Backup and WELLSCopy Restore' : Step 3, 'Restore Wells Copy
> Database' :
> Began Executing 2006-10-19 00:59:34
> Msg 3141, Sev 16: The database to be restored was named 'Wells'.
> Reissue the statement using the WITH REPLACE option to overwrite the
> 'WELLScopy'
> database. [SQLSTATE 42000]
> Msg 3013, Sev 16: RESTORE DATABASE is terminating abnormally. [SQLSTATE 42000]
>
> Here is the backup command and restore command.
> BACKUP DATABASE [Wells] TO Dbackup_WELLS
> WITH INIT, NOUNLOAD, NAME = N'Wells', SKIP, STATS=10, NOFORMAT
>
> restore database CHARITYDBCOPY
> from dbackup_charitydb
> with
> move 'CHARITYDB_Data' to 'o:\Data\CHARITYDBCOPY_Data.MDF',
> move 'CHARITYDB_Log' to 'o:\Data\CHARITYDBCOPY_Log.LDF'
>
> I tried to duplicate this issue in our test environment and it restored
> successfully every time. I did manage to break it by creating a new database
> with a totally different name then try to restore over it and received the
> error message.
> BOL says it performs a safety check if the REPLACE options is not used. If
> so, why has the restore work for a very long time and now decide to break.
> Also, why is it allowing me to restore successfully in test without using the
> REPLACE option.
> I am so confused...
> BOL...
> When the REPLACE option is not specified, a safety check occurs (which
> prevents overwriting a different database by accident). The safety check
> ensures that the RESTORE DATABASE statement will not restore the database to
> the current server if:
> The database named in the RESTORE statement already exists on the current
> server, and
> The database name is different from the database name recorded in the backup
> set.
>
|||Hi Tibor,
Thanks for the repsonse. We finally found the actual problem. Someone
restored the copy data outside of the normal job. Once we dropped and
recreated the job functioned as normal. Very strange behavior I must add.
"Tibor Karaszi" wrote:

> A guess is that the source database has grown, so the backup need say 10GB for one of the database
> files, but the existing database file only has, say, 8GB for that file.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "FredG" <FredG@.discussions.microsoft.com> wrote in message
> news:1D2AF5E1-9337-4F55-84EE-B4711171D7C9@.microsoft.com...
>

backup and restore a database

Dear all,
When i backup a database to a device(file) and then restore it into other
computer. The user always use to know the name of the database in order to
restore the database, can i make a backup to user without know the name of
the database to success to restore?Joe
I don't understand. Do you want to pass to BACKUP command a database name as
a parameter?
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:4E97E1F0-DC3E-4994-9F0A-0104F2F26979@.microsoft.com...
> Dear all,
> When i backup a database to a device(file) and then restore it into other
> computer. The user always use to know the name of the database in order to
> restore the database, can i make a backup to user without know the name of
> the database to success to restore?|||You can restore a user database backup to whatever database
name you want. The user doesn't have to specify the original
name of the database that was backed up.
You can find samples of how to do this in books online under
the topic: How to restore a database with a new name
or check the following link:
http://msdn.microsoft.com/library/d...>
kpc_6ng9.asp
-Sue
On Wed, 28 Sep 2005 01:03:03 -0700, Joe
<Joe@.discussions.microsoft.com> wrote:

>Dear all,
>When i backup a database to a device(file) and then restore it into other
>computer. The user always use to know the name of the database in order to
>restore the database, can i make a backup to user without know the name of
>the database to success to restore?

Backup and restore - What is the preffered way?

What is the preferred way for Backup and Restore? Maintenance plan wizard
or command line scripts?
Also, to setup email notifications on a sql box, what do we need (outlook
client..) on the server box? Is there a step by step document online to
setup this?
Plus please post some links to backup command scripts pages.
Thanks
BVR"Uhway" <vbhadharla@.sbcglobal.net> wrote in message
news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> What is the preferred way for Backup and Restore? Maintenance plan wizard
> or command line scripts?
T-SQL scheduled using SQL Server Agent Service
> Also, to setup email notifications on a sql box, what do we need (outlook
> client..) on the server box? Is there a step by step document online to
> setup this?
You need outlook 2000 onwards installed on the box SQL is installed. SQL
Server is going to be a member of a domain and a MAPI mail server has be to
used (e.g Exchange)
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/default.mspx
> Plus please post some links to backup command scripts pages.
The BOOKS Online (get the updated version from www.microsoft.com/sql) is
more then enough as a resource for writing T-SQL for Backup/Restore
> Thanks
> BVR
>
Cheers
Gill|||http://weblogs.sqlteam.com/tarad
Tara has some good backup/restore scripts. She has a standard version and a
SQL LiteSpeed version.
"Uhway" <vbhadharla@.sbcglobal.net> wrote in message
news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> What is the preferred way for Backup and Restore? Maintenance plan wizard
> or command line scripts?
> Also, to setup email notifications on a sql box, what do we need (outlook
> client..) on the server box? Is there a step by step document online to
> setup this?
> Plus please post some links to backup command scripts pages.
> Thanks
> BVR
>|||"Sarbjit Gill" <ssgill.no.spam@.no.spam.hotmail.com> wrote in message
news:%23hl3NHa9EHA.1408@.TK2MSFTNGP10.phx.gbl...
> "Uhway" <vbhadharla@.sbcglobal.net> wrote in message
> news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> > What is the preferred way for Backup and Restore? Maintenance plan
wizard
> > or command line scripts?
> T-SQL scheduled using SQL Server Agent Service
> >
> > Also, to setup email notifications on a sql box, what do we need
(outlook
> > client..) on the server box? Is there a step by step document online to
> > setup this?
> You need outlook 2000 onwards installed on the box SQL is installed. SQL
> Server is going to be a member of a domain and a MAPI mail server has be
to
> used (e.g Exchange)
>
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/default.mspx
This is not true. Yes, you need a MAPI client, but you can seti it up to
use an SMTP server. In fact that's what I find to be the most stable, set
up an SMTP server on the same box as the SQL Server and use that to forward
outgoing email. This eliminates the problem of the mail client locking up
due to time outs.
> >
> > Plus please post some links to backup command scripts pages.
> The BOOKS Online (get the updated version from www.microsoft.com/sql) is
> more then enough as a resource for writing T-SQL for Backup/Restore
> >
> > Thanks
> > BVR
> >
> >
> Cheers
> Gill
>
>|||Thanks
BVR
"Derrick Leggett" <derrickleggett@.yahoo.com> wrote in message
news:OCYipwc9EHA.2788@.TK2MSFTNGP15.phx.gbl...
> http://weblogs.sqlteam.com/tarad
> Tara has some good backup/restore scripts. She has a standard version and
a
> SQL LiteSpeed version.
>
> "Uhway" <vbhadharla@.sbcglobal.net> wrote in message
> news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> > What is the preferred way for Backup and Restore? Maintenance plan
wizard
> > or command line scripts?
> >
> > Also, to setup email notifications on a sql box, what do we need
(outlook
> > client..) on the server box? Is there a step by step document online to
> > setup this?
> >
> > Plus please post some links to backup command scripts pages.
> >
> > Thanks
> > BVR
> >
> >
>

Backup and restore - What is the preffered way?

What is the preferred way for Backup and Restore? Maintenance plan wizard
or command line scripts?
Also, to setup email notifications on a sql box, what do we need (outlook
client..) on the server box? Is there a step by step document online to
setup this?
Plus please post some links to backup command scripts pages.
Thanks
BVR"Uhway" <vbhadharla@.sbcglobal.net> wrote in message
news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> What is the preferred way for Backup and Restore? Maintenance plan wizard
> or command line scripts?
T-SQL scheduled using SQL Server Agent Service
> Also, to setup email notifications on a sql box, what do we need (outlook
> client..) on the server box? Is there a step by step document online to
> setup this?
You need outlook 2000 onwards installed on the box SQL is installed. SQL
Server is going to be a member of a domain and a MAPI mail server has be to
used (e.g Exchange)
http://www.microsoft.com/resources/...us/default.mspx[vbco
l=seagreen]
> Plus please post some links to backup command scripts pages.[/vbcol]
The BOOKS Online (get the updated version from www.microsoft.com/sql) is
more then enough as a resource for writing T-SQL for Backup/Restore
> Thanks
> BVR
>
Cheers
Gill|||http://weblogs.sqlteam.com/tarad
Tara has some good backup/restore scripts. She has a standard version and a
SQL LiteSpeed version.
"Uhway" <vbhadharla@.sbcglobal.net> wrote in message
news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> What is the preferred way for Backup and Restore? Maintenance plan wizard
> or command line scripts?
> Also, to setup email notifications on a sql box, what do we need (outlook
> client..) on the server box? Is there a step by step document online to
> setup this?
> Plus please post some links to backup command scripts pages.
> Thanks
> BVR
>|||"Sarbjit Gill" <ssgill.no.spam@.no.spam.hotmail.com> wrote in message
news:%23hl3NHa9EHA.1408@.TK2MSFTNGP10.phx.gbl...
> "Uhway" <vbhadharla@.sbcglobal.net> wrote in message
> news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
wizard[vbcol=seagreen]
> T-SQL scheduled using SQL Server Agent Service
(outlook[vbcol=seagreen]
> You need outlook 2000 onwards installed on the box SQL is installed. SQL
> Server is going to be a member of a domain and a MAPI mail server has be
to
> used (e.g Exchange)
>
http://www.microsoft.com/resources/...lt
.mspx
This is not true. Yes, you need a MAPI client, but you can seti it up to
use an SMTP server. In fact that's what I find to be the most stable, set
up an SMTP server on the same box as the SQL Server and use that to forward
outgoing email. This eliminates the problem of the mail client locking up
due to time outs.

> The BOOKS Online (get the updated version from www.microsoft.com/sql) is
> more then enough as a resource for writing T-SQL for Backup/Restore
> Cheers
> Gill
>
>|||Thanks
BVR
"Derrick Leggett" <derrickleggett@.yahoo.com> wrote in message
news:OCYipwc9EHA.2788@.TK2MSFTNGP15.phx.gbl...
> http://weblogs.sqlteam.com/tarad
> Tara has some good backup/restore scripts. She has a standard version and
a
> SQL LiteSpeed version.
>
> "Uhway" <vbhadharla@.sbcglobal.net> wrote in message
> news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
wizard[vbcol=seagreen]
(outlook[vbcol=seagreen]
>

Backup and restore - What is the preffered way?

What is the preferred way for Backup and Restore? Maintenance plan wizard
or command line scripts?
Also, to setup email notifications on a sql box, what do we need (outlook
client..) on the server box? Is there a step by step document online to
setup this?
Plus please post some links to backup command scripts pages.
Thanks
BVR
"Uhway" <vbhadharla@.sbcglobal.net> wrote in message
news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> What is the preferred way for Backup and Restore? Maintenance plan wizard
> or command line scripts?
T-SQL scheduled using SQL Server Agent Service
> Also, to setup email notifications on a sql box, what do we need (outlook
> client..) on the server box? Is there a step by step document online to
> setup this?
You need outlook 2000 onwards installed on the box SQL is installed. SQL
Server is going to be a member of a domain and a MAPI mail server has be to
used (e.g Exchange)
http://www.microsoft.com/resources/d...s/default.mspx
> Plus please post some links to backup command scripts pages.
The BOOKS Online (get the updated version from www.microsoft.com/sql) is
more then enough as a resource for writing T-SQL for Backup/Restore
> Thanks
> BVR
>
Cheers
Gill
|||http://weblogs.sqlteam.com/tarad
Tara has some good backup/restore scripts. She has a standard version and a
SQL LiteSpeed version.
"Uhway" <vbhadharla@.sbcglobal.net> wrote in message
news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
> What is the preferred way for Backup and Restore? Maintenance plan wizard
> or command line scripts?
> Also, to setup email notifications on a sql box, what do we need (outlook
> client..) on the server box? Is there a step by step document online to
> setup this?
> Plus please post some links to backup command scripts pages.
> Thanks
> BVR
>
|||"Sarbjit Gill" <ssgill.no.spam@.no.spam.hotmail.com> wrote in message
news:%23hl3NHa9EHA.1408@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> "Uhway" <vbhadharla@.sbcglobal.net> wrote in message
> news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
wizard[vbcol=seagreen]
> T-SQL scheduled using SQL Server Agent Service
(outlook
> You need outlook 2000 onwards installed on the box SQL is installed. SQL
> Server is going to be a member of a domain and a MAPI mail server has be
to
> used (e.g Exchange)
>
http://www.microsoft.com/resources/d...s/default.mspx
This is not true. Yes, you need a MAPI client, but you can seti it up to
use an SMTP server. In fact that's what I find to be the most stable, set
up an SMTP server on the same box as the SQL Server and use that to forward
outgoing email. This eliminates the problem of the mail client locking up
due to time outs.

> The BOOKS Online (get the updated version from www.microsoft.com/sql) is
> more then enough as a resource for writing T-SQL for Backup/Restore
> Cheers
> Gill
>
>
|||Thanks
BVR
"Derrick Leggett" <derrickleggett@.yahoo.com> wrote in message
news:OCYipwc9EHA.2788@.TK2MSFTNGP15.phx.gbl...
> http://weblogs.sqlteam.com/tarad
> Tara has some good backup/restore scripts. She has a standard version and
a[vbcol=seagreen]
> SQL LiteSpeed version.
>
> "Uhway" <vbhadharla@.sbcglobal.net> wrote in message
> news:ev0apRU9EHA.2804@.TK2MSFTNGP15.phx.gbl...
wizard[vbcol=seagreen]
(outlook
>

Backup and Restore - Config script

Hi all, how can I move my data from one Sql Server to a
new one I installed recently?, I mean, I want all my
databases and data (I created) that I have in my old
Server be copied in my new one. Is it just as simple as
making a Backup and then Restore my data?. Can I have the
same name for my Sql Server, if my new server is in a
different domain?. And one more question, I want to see
my actual Sql Server configuration, I mean when I
installed I chose some options I don't remember now, for
example: case sensitive, insensitive, dictionary order,
etc. So when I install my new SQL server I can pick the
same options and my new Server will act as my old one.
That's what I have planned!, I hope you can help me.
Thanks in advance
Freddy E.
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Freddy E." <freddye@.discussions.microsoft.com> wrote in message
news:1d61801c45451$379ee1a0$a601280a@.phx.gbl...
> Hi all, how can I move my data from one Sql Server to a
> new one I installed recently?, I mean, I want all my
> databases and data (I created) that I have in my old
> Server be copied in my new one. Is it just as simple as
> making a Backup and then Restore my data?. Can I have the
> same name for my Sql Server, if my new server is in a
> different domain?. And one more question, I want to see
> my actual Sql Server configuration, I mean when I
> installed I chose some options I don't remember now, for
> example: case sensitive, insensitive, dictionary order,
> etc. So when I install my new SQL server I can pick the
> same options and my new Server will act as my old one.
> That's what I have planned!, I hope you can help me.
> Thanks in advance
> Freddy E.

Backup and Restore - Config script

Hi all, how can I move my data from one Sql Server to a
new one I installed recently?, I mean, I want all my
databases and data (I created) that I have in my old
Server be copied in my new one. Is it just as simple as
making a Backup and then Restore my data?. Can I have the
same name for my Sql Server, if my new server is in a
different domain?. And one more question, I want to see
my actual Sql Server configuration, I mean when I
installed I chose some options I don't remember now, for
example: case sensitive, insensitive, dictionary order,
etc. So when I install my new SQL server I can pick the
same options and my new Server will act as my old one.
That's what I have planned!, I hope you can help me.
Thanks in advance
Freddy E.Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Server
s
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Freddy E." <freddye@.discussions.microsoft.com> wrote in message
news:1d61801c45451$379ee1a0$a601280a@.phx
.gbl...
> Hi all, how can I move my data from one Sql Server to a
> new one I installed recently?, I mean, I want all my
> databases and data (I created) that I have in my old
> Server be copied in my new one. Is it just as simple as
> making a Backup and then Restore my data?. Can I have the
> same name for my Sql Server, if my new server is in a
> different domain?. And one more question, I want to see
> my actual Sql Server configuration, I mean when I
> installed I chose some options I don't remember now, for
> example: case sensitive, insensitive, dictionary order,
> etc. So when I install my new SQL server I can pick the
> same options and my new Server will act as my old one.
> That's what I have planned!, I hope you can help me.
> Thanks in advance
> Freddy E.

Backup and Restore - Config script

Hi all, how can I move my data from one Sql Server to a
new one I installed recently?, I mean, I want all my
databases and data (I created) that I have in my old
Server be copied in my new one. Is it just as simple as
making a Backup and then Restore my data?. Can I have the
same name for my Sql Server, if my new server is in a
different domain?. And one more question, I want to see
my actual Sql Server configuration, I mean when I
installed I chose some options I don't remember now, for
example: case sensitive, insensitive, dictionary order,
etc. So when I install my new SQL server I can pick the
same options and my new Server will act as my old one.
That's what I have planned!, I hope you can help me.
Thanks in advance
Freddy E.Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Freddy E." <freddye@.discussions.microsoft.com> wrote in message
news:1d61801c45451$379ee1a0$a601280a@.phx.gbl...
> Hi all, how can I move my data from one Sql Server to a
> new one I installed recently?, I mean, I want all my
> databases and data (I created) that I have in my old
> Server be copied in my new one. Is it just as simple as
> making a Backup and then Restore my data?. Can I have the
> same name for my Sql Server, if my new server is in a
> different domain?. And one more question, I want to see
> my actual Sql Server configuration, I mean when I
> installed I chose some options I don't remember now, for
> example: case sensitive, insensitive, dictionary order,
> etc. So when I install my new SQL server I can pick the
> same options and my new Server will act as my old one.
> That's what I have planned!, I hope you can help me.
> Thanks in advance
> Freddy E.