1) Are you using linked tables? If you, was the password saved when making them

2) Are you using DSN-less connections?

see http://www.connectionstrings.com/ for a list of connectionstrings.

3)You shouldn't use sa for...

Thanks for pointing that out.

Very likely.

Is the script holding locks during its executions?

Any cursors?

Use a left join instead of an inner join.

SELECT JPT.JobPosting_ID,

ISNULL(MADT.ApplicationsReceived,0),

 JPT.Job_Code,

 JPT.Job_Title,

 JPT.Job_Posting_Date,

 JPT.Job_Location_Type,

 JPT.Job_Location

FROM

 Job_Posting_Table JPT

LEFT JOIN /*jobpostings can be without madt, ApplicationsReceived will be null then*/

 (

 SELECT JobPosting_ID, COUNT(*) ApplicationsReceived

 FROM

  Mgmt_App_Detail_Table

 GROUP BY JobPosting_ID) MADT

ON

 JPT.JobPosting_ID...

unique index:

pro: speed up selects,DRI

cons: slows updates, deletes, inserts as the index needs to be maintained, space used

use : mostly if the fields are frequently searched upon

unique constraint:

pro: still maintains uniqueness, doesn't...

If you are not using the 64 bit versions of w3k & sql 2000, you have to use the /PAE boot switch and set the memory for sql server (fixed)...

My understanding was that if someone reads a row in the database then this row is locked for the duration of the read and that if someone tries to update...

It could be that the default database for the ASP was changed.

Like is faster since it can use indexes. (with the wildcard at the right)

Left is applied to all records. (no index)

You're welcome.

Select distinct Have_Not_Type1.recID

From

(select distinct map.recID

from table1 map

left join table2 ON map.recID = table2.ID AND table2.type=1

WHERE table2.ID IS NULL

) AS Have_Not_Type1

INNER JOIN table2 Have_Other_type on Have_Not_Type1.recID=Have_Other_type.table2.ID

and (Have_Other_type.type =0 OR Have_Other_type.type=2...

Is your sql server set up to only allow Windows authentication, or Windows and SQL authentication?

In order to use windows authentication, you need to put the servers in a domain.

If they can't be in one, you have to use sql-authentication.

You can make some basic guesses which SQL statements are sent by using the sql profiler.

They delete from tables in the same order?

Any options specified update ... WITH ... ?

The error is caused by next run date which can be 0

a simple workaround

CASE

WHEN msdb..sysjobschedules.next_run_date =0 THEN NULL

ELSE cast(cast(msdb..sysjobschedules.next_run_date as varchar(15)) as datetime)

END AS next_run_date

,