Thank you Greg. I know that. I run quite a few jobs and schedule them to a certain time and everything is working fine. Sorry if I did not explain...

If I were you I will just open the design table and then, select the relationship icon. Then, print screen and paste it to your document or presentation. If you...

I am assuming that the domain account has admin rights, if not add the account to the admins group then try it again.

When added, did you use "\\domain\userID" syntax...

aRE YOU RUNNING sql 7 or 2000? sp_renamedb is a basic store proc in the master db. I copied the statement in case you need it, but you can go...

Thank you for all your input. I did figured it out. Here is the way it worked.

case_tab.DATE_CLOSED_DATE >= CONVERT(varchar(12), DATEADD([day], - 90, GETDATE()), 112)

Instea of trying to convert the date_closed_date...

Thanks Gregory. The variable I need to use is getdate() because I am pulling the data WHERE date_closed_date is equal to today's date - 90 days.

select convert(varchar(12), DATE_CLOSED_DATE, 112)AS...

When tried to change, did you enter the account as the user id or the domain name and user id (user or \\domainname\user)? Is the domain admin added to the...

Thanks Steve.

I did work yesterday a little bit more and so far I got SQL to use date be able to use dateadd function.

Still need to work more...

Thanks Steve. I already used that one. My problem is that the field first_m_date is not a datetime field in SQL Server due to the BBX setting. We get the...

Back again. I did check the table design and what happened is this:

The data comes from a system called BBX and the date data type in that system is character....

Thanks Andy. I did check everything, but the data type in my original table. For some reason who ever designed this db, used char for the dates instead of datetime....

There is an article here that could help. I used the main suggestions and work fine for me.

Article: Copying DTS Packages To a Different Server

By: Andy Warren

Just go to Resources,...

For the two issues you entered today, I can assume that both have to do with SQL Agent not being able to restart properly after reboot.

The error in this...

Sorry, I forgot. It looks like it is a permission issue. Are you set your authentication for SQL and NT?

To figure out exactly what could be the cause of the failure set a log file. When you run the package this log will pin point exatly to the error....