Scheduling in SQL server 2000

Hi all,

I have a case :

I have an employee SQL-View (not table) in my sql server 2000 database. This view actually connect to an oracle database server, because all our employee data is located on the oracle database server.

This linked server soon proven to be the cause of poor application performance (response time is very slow). So we decide to put a local copy of employee table in our sql server 2000 database. We have successfully copy it to our database. But the most up-to-date employee data is still reside on oracle server. To deal with this problem we need to scheduling a sinchronization between sqlserver 2000 and oracle everyday at 01:00 o'clock midnight.

I never get task like this before, how to make a scheduling in sql server 2000? my friend suggest a dts scheduling but unfortunately I haven't found any tutorial about this for beginner

thanks

You could just schedule a linked server INSERT INTO statement or use the DTS wizard to create a package and create a SQL Server Agent JOB to run at the above time. If you are not the DBA SQL Server Agent wil need a service account with Admin permissions to run your package through JOBs. Try the links below for more about SQL Server Agent permissions and DTS sample code. Hope this helps.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_8sdm.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_4jxo.asp

http://www.sqldts.com

Schedule and Delivery processor cannot connect

Hello,
I'm getting the following error on the application log of the event viewer:
Schedule and Delivery processor cannot connect to the report server database.
However I have no trouble to test some reports (e.g. the sample reports provided with reporting services).
What could be wrong with my configuration?
Thanks
CesarCan you look in the reportserverservice<date>.log files for more
information.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Cesar" <Cesar@.discussions.microsoft.com> wrote in message
news:BAF05421-386E-4712-8503-A304A1626C24@.microsoft.com...
> Hello,
> I'm getting the following error on the application log of the event
viewer:
> Schedule and Delivery processor cannot connect to the report server
database.
> However I have no trouble to test some reports (e.g. the sample reports
provided with reporting services).
> What could be wrong with my configuration?
> Thanks
> Cesar|||Hello daniel,
On one line of the log says:
"Cannot open database requested in login 'Report Server'. Login fails"
How can I fix that ?
But I had no errors during set up when I configured the account with which reporting services would use to connect to the database.
"Daniel Reib [MSFT]" wrote:
> Can you look in the reportserverservice<date>.log files for more
> information.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Cesar" <Cesar@.discussions.microsoft.com> wrote in message
> news:BAF05421-386E-4712-8503-A304A1626C24@.microsoft.com...
> > Hello,
> >
> > I'm getting the following error on the application log of the event
> viewer:
> >
> > Schedule and Delivery processor cannot connect to the report server
> database.
> >
> > However I have no trouble to test some reports (e.g. the sample reports
> provided with reporting services).
> >
> > What could be wrong with my configuration?
> > Thanks
> > Cesar
>
>

schedule a ssis job

I created a ssis package on my local developer sql server, the package is to connect to another sql server, and export a view to an excel file and send an email with excel attachment.

If I run the package manually it works great.

But now I want to schedule it to run as a job in my local sql server, I cannot make it right.

What I did is:

Create my credential to map to my windows log in
Then create a proxy account to map credential.
Then run the job using my proxy account, but I keep getting errors, . The package execution failed. The step failed.

I cannot get more detailed info.

Please advise.

ThanksThe end of this KB article has instructions for getting detailed info:
http://support.microsoft.com/kb/918760