Re: SQL Server Agent Query

Neil,

Since SQL 7.0 wasn't officially out when we released PTF 1 of the
SQL Agent, we couldn't mention SQL 7.0...but SQL 7.0 is supported.
On the SQL Agent under SQL Server 7.0, recovery for the command-line
program is controlled through the following option:

     /RECOVERY:Yes|No       (Default is "Yes")

So, for example, here is a set of restore commands:

     sqldsmc /restorefull:pubs,06231999101053.db   /recovery:no
     sqldsmc /restoreincr:pubs,06241999081002.log  /recovery:no
     sqldsmc /restoreincr:pubs,06251999120434.log  /recovery:no
     sqldsmc /restoreincr:pubs,06261999052023.log  /recovery:yes

Notice that the last incremental is restored with
the /recovery:yes option which tells the SQL Server to run
recovery after the restore is complete.
(The GUI program handles this for you automatically as long as you
choose all of the objects to restore at once.)

As far as futures...all three things that you mention are in our plans
to add to the SQL Agent.  At this time, I cannot give specific dates,
but we do know that you want them and we are working on them.

Del Hoobler
ADSM Agent Development

> Can anybody help me with a query about the SQL Server Connect Agent?
>
> We use the SQL Server Connect Agent v1.1.1 to backup databases on SQL
> Server 7. We use a mixture of nightly full backups and transaction log
> backups during the day.
>
> Suppose I were using SQL Server (eg Enterprise Manager) to restore a
> database. When I restored the database using the full backup as a starting
> point, I would have to specify whether or not SQL Server should roll back
> any uncommitted transactions using the WITH RECOVERY / WITH NORECOVERY
> option. Assuming I needed to subsequently restore a number of transaction
> logs, I would specify WITH NORECOVERY.
>
> If I were using the SQL Connect Agent for ADSM (eg SQLDSMC /RESTOREFULL)
> how would I make this distinction?
>
> BTW, can anybody at IBM give me some idea of a 'roadmap' for the ADSM SQL
> Server Connect Agent? What I'm looking for is timescales for the
> introduction of things like Differential database backups (new in SQL
> Server 7), Web-based GUI for remote administration, automatic deletion of
> obsolete database backups, etc.
>
> This info will help us to decide how widely we use the Connect Agent. In a
> lot of cases, we gain a lot more by doing on-line backups to disk under the
> SQL Server Agent and backing these up using the 'normal' backup/archive
> client.