Database backup using Scheduled Tasks

[Magnus.Moraberg]

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.

 

[Pegasus \(MVP\)]

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.

The standard approach is to create and use a dedicated account for scheduled
tasks (e.g. "Scheduler") with a strong but non-expiring password.

 

[Erland Sommarskog]

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?

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

--
Erland Sommarskog, SQL Server MVP, (e-mail address removed)

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/previousversions/books.mspx

 

[patrick61z]

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

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.

 

[Erland Sommarskog]

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.

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, (e-mail address removed)

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/previousversions/books.mspx

 

[patrick61z]

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?

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.