Backing up SQL

Help, I'm in a time crunch so I need answers fast.  We are a complete NT4 shop, servers to workstations, one of our servers is running SQL 6.5, Cheyenne's ArcServe 6.5 (build 620), open file backup agent and an eval of the SQL agent for ArcServe.  The SQL restores are the problem.  Table Restores are fine, Database Restores require intervention but they work (you must manually recreate the database object.)  Database Device Restores work for one device at a time.  However, attempting to restore multiple database devices does not.  I am not really looking for a specific fix for our issues, so much as someone who has done this and who has had problems they have overcome.  I need someone who can provide some important tips and tricks to make this all work.  I am giving a lot of points away on this one to the individual who provide the best and the most, the quickest.  
   
LVL 1
tkd_jayAsked:
Who is Participating?
 
gmoriakCommented:
Here's reasoning for the way it is:

The LOAD DATABASE command takes a database name - this is good.  It allows you to backup a database and restore it under a new name.  The database name is not hard coded into the database.  The admin functions you speak of are show stoppers.  They had better act as expected.  If they automatically created devices or databases, this might lead to unexpected results (though they are the results you personally want).  I think of this "limitation" more as safety features.
0
 
tkd_jayAuthor Commented:
Edited text of question
0
 
tkd_jayAuthor Commented:
Edited text of question
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
tkd_jayAuthor Commented:
Edited text of question
0
 
gmoriakCommented:
You could create scripts to do your work.  e.g.

/* loadmydatabase.sql */
create database mydatabase ....
go
load database mydatabse ...
go

Then run the scripts using

isql.exe .... -i loadmydatabase.sql

Run isql /? for all command line parameters.  The same could be done to resolve your other problems.  You can schedule these commands to run as you want etc.
0
 
tkd_jayAuthor Commented:
We understand that we can use scripts, it just seems to us that the restore process should be more seemless than it seems to be.  
0
 
gmoriakCommented:
Don't shoot the messenger
0
 
tkd_jayAuthor Commented:
No shots fired from this direction.  I take it you have already run into this situation?
0
 
tkd_jayAuthor Commented:
Thanks for the info, but no thanks, you confirmed what we feared.  We considered giving you a "C" since it wasn't the answer we wanted to hear.  But we don't shoot the messenger and it isn't your fault it doesn't work as seamless as it should.  So since you gave the only answer you could and it appears to be the correct one you get an A and all 500 pts.  Enjoy and thanks for nothing, : )

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.