Scheduled job for backup

My scheduled job didnt run. there's no error message that appear on my my
sql server even when i set up the job, that' why i concluded that i did it
correctly. What could be the problem?
Thanks a lot!Verify that Agent service is running.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"newbie" <newbie@.discussions.microsoft.com> wrote in message
news:FEC20577-CA41-44A0-AF41-366835F62A54@.microsoft.com...
> My scheduled job didnt run. there's no error message that appear on my my
> sql server even when i set up the job, that' why i concluded that i did it
> correctly. What could be the problem?
> Thanks a lot!

Schedule a DTS in SSIS

Can someone point me out how to create a job to start a schedule of a DTS package?

Not encapsulating the DTS into a SSIS package.

I didn′t find even a way to run the package without opening it with the DTS Designer.

Thanks in advance

You don't have dtsrun.exe available? I'm not sure how to install this util from SQL 2000, maybe it's just a copy/paste since all other runtime components might be already installed to support the DTS designer... But first check if DTSRUN is not already on your machine. Then you can use it to schedule a package in the SQL Server Agent. If you need help to construct the paramters DTSRUN expects, try DTSRUNUI, this can construct the parameters for you...|||

If I have SQL Server 2000, I can run dtsrun/dtsrunui.

If I have SQL Server 2005, I can run dtexec/dtexecui.

But with dtsrun I access SQL Server 2000 DTS Server, not SQL Server 2005 Server.

and dtexec(ui) does not show you DTS (legacy) packages.

In a side by side installation I see that you can schedule packages in SQL Server 2000....but If you only want to use SQL Server 2005, and still schedule DTS packages, how can it be done?

|||

I understand... I didn't play much with DTS packages in SQL 2005 so just some ideas...

Is it possible to use DTSRUN with SQL2005? Did you try that? Maybe it doesn't work with DTS packages stored in MSDB, but perhaps storing them in files is a solution for you...

What's the reason for you not using the Execute DTS 2000 Package task in SSIS?

|||

I tried DTSRUN with SQL2005 but I can only access SQL2000....

Checking how to include a SSIS package with a Execute DTS 2000 Package task, realized that I have to access a SQL2000, too.

The statement is, why we have a way to 'upload' legacy DTS packages to SQL2005, if we cannot schedule them?

(or I didn't manage to get it)

The scenario is use the existing packages without any SQL2000 Server