Database backup using Scheduled Tasks

[Guest Magnus.Moraberg@gmail.com]

Hi,

 

I'm working on a Windows 2000 machine which hosts a SQL 2005 Express

Database.

 

This database is backed up using the following method -

 

http://www.sqldbatips.com/showarticle.asp?ID=27

 

As part of this method, I have a Task which is scheduled to run once a

day. All words fine until I need to change my password. When I am

prompted to change my password every month or so, I need to go back

into the Scheduler and update my password there also. Otherwise my

backup process will fail. How can I solve this problem?

 

Another problem is that I will be soon handing the database over to

another employee at the company who will then be in charge of

maintaining it. Therefore I will have to configure the Scheduler to

run from his account. I'm sure there's a better approach...

 

Thanks for your help,

 

Barry.

[Guest Pegasus \(MVP\)]

<Magnus.Moraberg@gmail.com> wrote in message

news:0c1db6c7-a7ba-49d3-817c-1b29d1094d5e@u29g2000pro.googlegroups.com...<span style="color:blue">

> Hi,

>

> I'm working on a Windows 2000 machine which hosts a SQL 2005 Express

> Database.

>

> This database is backed up using the following method -

>

> http://www.sqldbatips.com/showarticle.asp?ID=27

>

> As part of this method, I have a Task which is scheduled to run once a

> day. All words fine until I need to change my password. When I am

> prompted to change my password every month or so, I need to go back

> into the Scheduler and update my password there also. Otherwise my

> backup process will fail. How can I solve this problem?

>

> Another problem is that I will be soon handing the database over to

> another employee at the company who will then be in charge of

> maintaining it. Therefore I will have to configure the Scheduler to

> run from his account. I'm sure there's a better approach...

>

> Thanks for your help,

>

> Barry.</span>

 

The standard approach is to create and use a dedicated account for scheduled

tasks (e.g. "Scheduler") with a strong but non-expiring password.

[Guest Erland Sommarskog]

(Magnus.Moraberg@gmail.com) writes:<span style="color:blue">

> As part of this method, I have a Task which is scheduled to run once a

> day. All words fine until I need to change my password. When I am

> prompted to change my password every month or so, I need to go back

> into the Scheduler and update my password there also. Otherwise my

> backup process will fail. How can I solve this problem?</span>

 

Can't you create new user that you specify as the owner of this job?

 

--

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

 

Links for SQL Server Books Online:

SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx

SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

SQL 2000: http://www.microsoft.com/sql/prodinfo/prev...ions/books.mspx

[Guest patrick61z@yahoo.com]

On Nov 18, 2:27 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:<span style="color:blue">

> (Magnus.Morab...@gmail.com) writes:<span style="color:green">

> > As part of this method, I have a Task which is scheduled to run once a

> > day. All words fine until I need to change my password. When I am

> > prompted to change my password every month or so, I need to go back

> > into the Scheduler and update my password there also. Otherwise my

> > backup process will fail. How can I solve this problem?</span>

>

> Can't you create new user that you specify as the owner of this job?

></span>

 

Hah! I tried that at work, and the admins force password policy on the

new account as well. Still, that would be my vote too.

[Guest Greg D. Moore \(Strider\)]

<patrick61z@yahoo.com> wrote in message

news:15d3bec5-4cee-432d-9b7e-3898cd2b8864@d36g2000prf.googlegroups.com...<span style="color:blue">

> On Nov 18, 2:27 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:<span style="color:green">

>> (Magnus.Morab...@gmail.com) writes:<span style="color:darkred">

>> > As part of this method, I have a Task which is scheduled to run once a

>> > day. All words fine until I need to change my password. When I am

>> > prompted to change my password every month or so, I need to go back

>> > into the Scheduler and update my password there also. Otherwise my

>> > backup process will fail. How can I solve this problem?</span>

>>

>> Can't you create new user that you specify as the owner of this job?

>></span>

>

> Hah! I tried that at work, and the admins force password policy on the

> new account as well. Still, that would be my vote too.</span>

 

Bah... admins who force password changes every month, especially for

accounts like that, deserve to be shot.

 

There's far better ways to enforce security than forcing people to come up

with a new password every 30 days that they're going to end up writing down

in most cases or making non-secure.

 

Month_1: El3phant

Month_2: El3phant1

Month_3: El3phant2

Month_4: El3phant4

Month_5: Oh good, can go back to El3phant again.

 

 

 

--

Greg Moore

Ask me about lily, an RPI based CMC.

[Guest Erland Sommarskog]

(patrick61z@yahoo.com) writes:<span style="color:blue">

> Hah! I tried that at work, and the admins force password policy on the

> new account as well. Still, that would be my vote too.</span>

 

Hm, can't you make a local machine account? That should not be subject

to group policy.

 

But if you need a service account that has to be a domain account, why

don't you talk to your admin folks?

 

--

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

 

Links for SQL Server Books Online:

SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx

SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

SQL 2000: http://www.microsoft.com/sql/prodinfo/prev...ions/books.mspx

[Guest patrick61z@yahoo.com]

On Nov 20, 1:57 am, Erland Sommarskog <esq...@sommarskog.se> wrote:<span style="color:blue">

> (patrick...@yahoo.com) writes:<span style="color:green">

> > Hah! I tried that at work, and the admins force password policy on the

> > new account as well. Still, that would be my vote too.</span>

>

> Hm, can't you make a local machine account? That should not be subject

> to group policy.

>

> But if you need a service account that has to be a domain account, why

> don't you talk to your admin folks?

></span>

 

These sorts of jobs I want executed need too much network access for

local accounts, and I already did ask the admins to no avail. I think

that these sorts of practices are pretty much embraced to save on the

work researching the ramifications of doing something different (often

to a comically extreme extent) but on the bright side, if I keep my

protestations at a friendly academic level, I'm more likely to keep a

job.