|
|
|
Question : SQL Scheduled task problem
|
|
I am using SQL Server 2000 and have DTS Local Packages Setup which I am having to manually execute every day to perform data backups of my SQL Databases.
I am importing/exporting the data from SQL server database into an Access .mdb database which is located on a network drive.
I have been trying to configure these packages, using SQL Server Enterprise Manager, with a Schedule so that they automatically execute everyday. The problem is that when the scheduled package executes it fails due to the fact that it is unable to locate the destination Access Database on the network drive. It seems that the Schedule is only able to access the local drives ??
The network drive has the following name: mjmwork on 'mjmnas' (F:)
I have also tried adding \\mjnas\mjmwork\MJM Documents\.... etc to the Filename for the Destination Source during the Import/Export Wizard instead of using the browse function to select the filename, which would be displayed as:
F:\MJM Documents\Internal Projects\Project Control Database\SQL DataBackup\Auto_Project_Control_databackup_SQL.mdb
The Package Executes successfully when I manually start it but am unable to get this running using a scheduled job.
Any thoughts ??
|
Answer : SQL Scheduled task problem
|
|
Schedule Jobs run with the user who started the SQLSERVERAGENT windows service. Normally this service uses the local system account. Well, this account has no permission over network resources and it should remain that way.
What you can do is open Windows Services MMC, and change the login used to start SQLSERVERAGENT, defining a diferent user - one that has access to the network resource -, then restart SQLSERVERAGENT service.
(See picture)
|
|
|
|
|
|
|
