I would guess that the TDP account for SQL Server just has to be a
member of the db_backupoperator role in each database. Once you give it
this role in each database (including model) it will automatically have
this role in any new database (because new databases start off as copies
of model).
Ho
Del said...
> Maybe some subscribers on this list with this SQL Server configuration
> will share what they have done in their environment?
We don't currently have many SQL Servers that are multi-instance, but
here's what we've done on the ones that are. So far it seems to work
just fine. We cap
Not to nitpick, but you'd be better off putting the tablespaces into
backup mode one at a time in your shell script, because Oracle has to do
additional (larger) logging when a tablespace is in backup mode.
Basically it has to log OS block images instead of DB page or data
images. Anyway, if you h
tadata supplies
the file location that will be used by a restore unless you override that
specific file's location with the /RELOCATE and /TO clauses.
Make sense? Hope so. :o)
-Chris
_
From: Moses Show [mailto:[EMAIL PROTECTED]
Sent: Friday, August 27, 2004 9:23 AM
To: Leonard, Chr
Moses,
Your metadata shows the following 6 files: 3 data files named DWH_Data,
DWH_1_Data, and DWH_2_Data and 3 log files named DWH_Log, DWHPROD_Log, and
DWHPROD_Log1. However, your TDPSQLC RESTORE command is only relocating two
of them, DWH_Data and DWH_Log. Therefore, the other 4 files are tr
Hi Moses,
The way I do this is as follows. First of all, we use PasswordAccess=Prompt
in our dsm.opt. If it's possible to do this using Generate, I'd appreciate
somebody chiming in, because I could not figure that out.
Having said that, assume that I want to restore a backup made from MSSQLA
on
Jeff,
I didn't see anybody reply with anything better than what I know, so I
thought I'd chime in. To do this, you will need to use TDPSQLC to query the
TSM database for /ALL backups - not just the active ones. For example,
"tdpsqlc query tsm mydatabase /all". Then you need to parse the output,
Thanks Del. I will try to do just that.
The number of SQL Server instances and databases we have, plus the hardware
we currently have available (not to mention the admistrative issues
associated with restoring from one SQL Server node onto another in sqltdp!)
make doing "actual" restores of each
As long as I'm posting, here's a question for Del. There is one glaring
omission in the TDP client for SQL Server, namely the lack of any command
that would expose Microsoft's RESTORE VERIFYONLY command. This command
saves tons of time in verifying backups, since it greatly simplifies the
process
I am a SQL-Head (as Mark so elegantly put it), and one with more experience
than most. The fact that the DBAs can do a backup from SQL Enterprise Manager
(or whatever) does *not* prove that this is not a SQL Server error. It may,
sadly, give substantial evidence that they are stubborn or relative
John,
This may not help you right now, but in case you're wanting to throw SQL
Server out the Window because of this "feature," I thought I'd mention that
this will change in SQL Server 2005. As others have mentioned, SQL Server
2000 (and prior) must initialize all of the database pages before pr
11 matches
Mail list logo
