Disaster/recovery techniques

I have recently installed SQL Server 2000 on a newly acquired Windows
2003 server. The network admins also got Brightstor Agent for SQL
Server to interface with Brightstor ARCserve Backup for Windows
running on our backup server. I think I have a pretty good handle on
how to setup the SQL Server backups using a combination of
full/differential/transaction log backups to handle any recovery
required for the SQL Server databases.
What are the alternatives for backing up the Server itself for use in
recovery? Two approaches come to mind.
The first is not worry about backing up the server, in which case for
a recovery, I would have to reinstall all the software and service
packs to rebuild the environment. This would certainly require that I
have fully documented what applications (Windows 2003 server, SQL
Server, Outlook, Brightstor Agent, etc) and the install options that
were chosen. The rebuild process for this could take some time, and
there may be some issues that I haven't considered.
The second is to fully backup the server including the registry. If
everything were installed to the "C:\" drive, I could maybe get by
with just backing up the "C:\" drive and the registry. I do have a
weekend window where I could down the server to perform this task on a
weekly basis. Then for recovery I could just install an operating
system, restore from the backup of the "C:\" drive and registry and
proceed to my SQL Server recovery. Are there any problems with this
approach?
Finally, are there other techniques that I should consider? Any
websites or newsgroup threads on this topic would be greatly
appreciated.
Thanks Much, Lane LesperanceI prefere the first approach. it's the databases you should back up, not the
server.
Part of a good recovery plan is to document everything, so you can put the
server back to its original configuration before applying your backup files.
you can use the 2nd one, but to me it will take longer, and you need to
really test it on a test box to make sure you can recover your data that
way.
Steve Lin
MCDBA
"Lane Lesperance" <llesperance@.cooperpower.com> wrote in message
news:66feb5c.0404051118.e0472bf@.posting.google.com...
> I have recently installed SQL Server 2000 on a newly acquired Windows
> 2003 server. The network admins also got Brightstor Agent for SQL
> Server to interface with Brightstor ARCserve Backup for Windows
> running on our backup server. I think I have a pretty good handle on
> how to setup the SQL Server backups using a combination of
> full/differential/transaction log backups to handle any recovery
> required for the SQL Server databases.
> What are the alternatives for backing up the Server itself for use in
> recovery? Two approaches come to mind.
> The first is not worry about backing up the server, in which case for
> a recovery, I would have to reinstall all the software and service
> packs to rebuild the environment. This would certainly require that I
> have fully documented what applications (Windows 2003 server, SQL
> Server, Outlook, Brightstor Agent, etc) and the install options that
> were chosen. The rebuild process for this could take some time, and
> there may be some issues that I haven't considered.
> The second is to fully backup the server including the registry. If
> everything were installed to the "C:\" drive, I could maybe get by
> with just backing up the "C:\" drive and the registry. I do have a
> weekend window where I could down the server to perform this task on a
> weekly basis. Then for recovery I could just install an operating
> system, restore from the backup of the "C:\" drive and registry and
> proceed to my SQL Server recovery. Are there any problems with this
> approach?
> Finally, are there other techniques that I should consider? Any
> websites or newsgroup threads on this topic would be greatly
> appreciated.
> Thanks Much, Lane Lesperance

disable/enable all SQL Agent jobs in a non cursor approach

Is there a way to disable/enable all SQL Agent jobs using a set based
operation as opposed to a cursory approach that i can think of right now
If so, can one provide the SQL for itI don't think so, because you should be calling a stored procedure for each
job. (As opposed to updating a table somewhere in MSDB, which you shouldn't
do without fully understanding what else the procedure does.)
What is wrong with a cursor approach for this type of one-off, admin task?
On 2/28/05 2:53 PM, in article eGUAu8cHFHA.904@.tk2msftngp13.phx.gbl,
"Hassan" <fatima_ja@.hotmail.com> wrote:

> Is there a way to disable/enable all SQL Agent jobs using a set based
> operation as opposed to a cursory approach that i can think of right now
> If so, can one provide the SQL for it
>|||Nothing wrong, always heard dreaded things about cursors and was just trying
to see if one could do so in a set based approach ?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:BE4926C4.181D%ten.xoc@.dnartreb.noraa...
> I don't think so, because you should be calling a stored procedure for
each
> job. (As opposed to updating a table somewhere in MSDB, which you
shouldn't
> do without fully understanding what else the procedure does.)
> What is wrong with a cursor approach for this type of one-off, admin task?
>
>
> On 2/28/05 2:53 PM, in article eGUAu8cHFHA.904@.tk2msftngp13.phx.gbl,
> "Hassan" <fatima_ja@.hotmail.com> wrote:
>
>|||NO! Not when you have to call a stored procedure for each item in the set.
And like I said, for one-off admin tasks that you're not performing
regularly, I wouldn't spend too much time worrying about the performance of
your chosen approach. Just get the task done, and then work on doing
whatever you need to do to not require that task to be necessary in the
future.
On 2/28/05 11:43 PM, in article uDpX3khHFHA.2276@.TK2MSFTNGP15.phx.gbl,
"Hassan" <fatima_ja@.hotmail.com> wrote:

> Nothing wrong, always heard dreaded things about cursors and was just tryi
ng
> to see if one could do so in a set based approach ?

disable the BULTIN/admin then SQL Agent topped!

when i disabled the BULTIN/admin user in SQL 2000
i could start SQL Server service, but i couldn't start SQL Agent Service
does anyone know how to slove this prob
I also wanna know is it suitable to disable the BULTIN/admin user in SQL 200
than| when i disabled the BULTIN/admin user in SQL 2000,
i could start SQL Server service, but i couldn't start SQL Agent Service.
| does anyone know how to slove this prob?
I also wanna know is it suitable to disable the BULTIN/admin user in SQL
2000
|
| thanx
|
--
Checkout these articles:
PRB: SQL Server Agent Does Not Start and Displays Error 18456
http://support.microsoft.com/?id=237604
INF: How to Impede Windows NT Administrators from Administering
http://support.microsoft.com/?id=263712
Hope this helps,
--
Eric Cárdenas
SQL Server support|||thanx a lot, the article helps a lot.

Disable MSX Functionality

How do you stop an MSX server being an MSX server?
In other words, how do I get Enterprise Manager back to the state where
under SQL Server Agent\Jobs I don't get sub-folders of Local and
Remote, and I'm not allowed to target jobs at other servers?
Thanks.
DaveHi,
just force defection of all your target Servers. When the last target
server
is defected then your MSX functionality should stop automatically.
Regards
Bobby Henningsen
"Dave" <david.randall@.tradeweb.com> wrote in message
news:1132328870.648249.134860@.g49g2000cwa.googlegroups.com...
> How do you stop an MSX server being an MSX server?
> In other words, how do I get Enterprise Manager back to the state where
> under SQL Server Agent\Jobs I don't get sub-folders of Local and
> Remote, and I'm not allowed to target jobs at other servers?
> Thanks.
> Dave
>
---
Jeg beskyttes af den gratis SPAMfighter til privatbrugere.
Den har indtil videre sparet mig for at f? 712 spam-mails.
Betalende brugere f?r ikke denne besked i deres e-mails.
Hent gratis SPAMfighter her: www.spamfighter.dk|||Nice one, thanks!
Dave

Disable MSX Functionality

How do you stop an MSX server being an MSX server?
In other words, how do I get Enterprise Manager back to the state where
under SQL Server Agent\Jobs I don't get sub-folders of Local and
Remote, and I'm not allowed to target jobs at other servers?
Thanks.
Dave
Hi,
just force defection of all your target Servers. When the last target
server
is defected then your MSX functionality should stop automatically.
Regards
Bobby Henningsen
"Dave" <david.randall@.tradeweb.com> wrote in message
news:1132328870.648249.134860@.g49g2000cwa.googlegr oups.com...
> How do you stop an MSX server being an MSX server?
> In other words, how do I get Enterprise Manager back to the state where
> under SQL Server Agent\Jobs I don't get sub-folders of Local and
> Remote, and I'm not allowed to target jobs at other servers?
> Thanks.
> Dave
>
Jeg beskyttes af den gratis SPAMfighter til privatbrugere.
Den har indtil videre sparet mig for at f? 712 spam-mails.
Betalende brugere f?r ikke denne besked i deres e-mails.
Hent gratis SPAMfighter her: www.spamfighter.dk
|||Nice one, thanks!
Dave

Disable Job Steps

Hi
I have a job setup in SQL Server Agent (SQL 2005) that runs multiple
packages. Each package is run as a separate step in the job. I am busy
testing the job and want to skip some of the longer running packages for now.
Is there a way to disable a job step and then enable it again when I am
ready. Deleting the step and recreating it again is one option, but there
must be a better way
ThanksTake a look at
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/e158802c-c347-4a5d-bf75-c03e5ae56e6b.htm
"Trevor Howe" <TrevorHowe@.discussions.microsoft.com> wrote in message
news:13A6603B-003D-4BD8-805F-F37C8AC23A6F@.microsoft.com...
> Hi
> I have a job setup in SQL Server Agent (SQL 2005) that runs multiple
> packages. Each package is run as a separate step in the job. I am busy
> testing the job and want to skip some of the longer running packages for
> now.
> Is there a way to disable a job step and then enable it again when I am
> ready. Deleting the step and recreating it again is one option, but there
> must be a better way
> Thanks|||Trevor Howe wrote:
> Hi
> I have a job setup in SQL Server Agent (SQL 2005) that runs multiple
> packages. Each package is run as a separate step in the job. I am busy
> testing the job and want to skip some of the longer running packages for now.
> Is there a way to disable a job step and then enable it again when I am
> ready. Deleting the step and recreating it again is one option, but there
> must be a better way
> Thanks
On each job step you have to option to decide what to do on "Success"
and on "Failure". Here you can choose to go to certain step in the job
on e.g. "Success".
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||Thanks guys. That was fast!! I also found the solution about five minutes
after I sent out the original post. Would'nt it be nice if all responses were
as successful and quick as this one. Now for my next mind bender: What is the
first name of the founder of Microsoft - :0) - Jokes
""Steen Schlüter Persson (DK)"" wrote:
> Trevor Howe wrote:
> > Hi
> >
> > I have a job setup in SQL Server Agent (SQL 2005) that runs multiple
> > packages. Each package is run as a separate step in the job. I am busy
> > testing the job and want to skip some of the longer running packages for now.
> > Is there a way to disable a job step and then enable it again when I am
> > ready. Deleting the step and recreating it again is one option, but there
> > must be a better way
> >
> > Thanks
> On each job step you have to option to decide what to do on "Success"
> and on "Failure". Here you can choose to go to certain step in the job
> on e.g. "Success".
> --
> Regards
> Steen Schlüter Persson
> Database Administrator / System Administrator
>

Disable Job Steps

Hi
I have a job setup in SQL Server Agent (SQL 2005) that runs multiple
packages. Each package is run as a separate step in the job. I am busy
testing the job and want to skip some of the longer running packages for now
.
Is there a way to disable a job step and then enable it again when I am
ready. Deleting the step and recreating it again is one option, but there
must be a better way
ThanksTake a look at
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/e158802c-c347-4a5d-bf75-
c03e5ae56e6b.htm
"Trevor Howe" <TrevorHowe@.discussions.microsoft.com> wrote in message
news:13A6603B-003D-4BD8-805F-F37C8AC23A6F@.microsoft.com...
> Hi
> I have a job setup in SQL Server Agent (SQL 2005) that runs multiple
> packages. Each package is run as a separate step in the job. I am busy
> testing the job and want to skip some of the longer running packages for
> now.
> Is there a way to disable a job step and then enable it again when I am
> ready. Deleting the step and recreating it again is one option, but there
> must be a better way
> Thanks|||Trevor Howe wrote:
> Hi
> I have a job setup in SQL Server Agent (SQL 2005) that runs multiple
> packages. Each package is run as a separate step in the job. I am busy
> testing the job and want to skip some of the longer running packages for n
ow.
> Is there a way to disable a job step and then enable it again when I am
> ready. Deleting the step and recreating it again is one option, but there
> must be a better way
> Thanks
On each job step you have to option to decide what to do on "Success"
and on "Failure". Here you can choose to go to certain step in the job
on e.g. "Success".
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||Thanks guys. That was fast!! I also found the solution about five minutes
after I sent out the original post. Would'nt it be nice if all responses wer
e
as successful and quick as this one. Now for my next mind bender: What is th
e
first name of the founder of Microsoft - :0) - Jokes
""Steen Schlüter Persson (DK)"" wrote:

> Trevor Howe wrote:
> On each job step you have to option to decide what to do on "Success"
> and on "Failure". Here you can choose to go to certain step in the job
> on e.g. "Success".
> --
> Regards
> Steen Schlüter Persson
> Database Administrator / System Administrator
>