As far as I know, that isn't possible, since it would compromise the inherent security of Windows authentication by exposing the password. You could have a look in connectionstrings.com...

Those decimals at the ends of the rows don't convert into datetime values, I'm afraid. But seriously, I really think full-text indexing is the way to go on this....

That's closer, but we need the actual values in the insert statements. Do you see why? Somebody can just run your CREATE TABLE statements, then run your INSERT...

Andrew

I was being facetious - pointing out that it's always better to do your backups and restores through the command line than go through the fiddly GUI wizard. That...

No, INSERT statements. Many people won't bother to open a spreadsheet (may contain viruses), and of those that do, most won't have the time or inclination to import all...

Iain

Is it possible that SQL Server (or SQL Server Agent) wasn't running at the time the job was scheduled? Maybe somebody restarted the server, or perhaps if you have...

That makes sense. I usually find it takes about 25 minutes just to set up a restore through the GUI! That's why I always use a script.

John

Andrew

Do you still have the job history going back to when it was taking a long time? If you do, which job steps are showing the biggest improvement?

John

Then your package is not working properly, or maybe the e-mail that you don't get is filtered out by Mimesweeper or whatever you have on your mail system. Perhaps...

Rob

From those results, it looks as if step 2 runs every time the job runs - for the last five executions, certainly. What makes you think step 2 isn't...

Rob

Please run these two queries and post the results:

SELECT

s.step_id

,s.on_success_action

,s.on_success_step_id

,s.on_fail_action

,s.on_fail_step_id

FROM

msdb..sysjobs j

JOIN

msdb..sysjobsteps s

ON

j.job_id = s.job_id

WHERE

j.name = '<Job_Name>'

SELECT TOP (15)

h.step_id

,h.run_date

,h.run_time

,h.run_status

FROM

msdb..sysjobs j

JOIN

msdb..sysjobhistory h

ON

j.job_id = h.job_id

WHERE

j.name = '<Job_Name>'

ORDER BY

run_date DESC

,run_time DESC

John

Rob

Check that the first step not configured to "quit the job reporting success" when it succeeds. You need it to be configured to "go to the next step".

John

Yes, it's usually spelt lakh and is mainly used in India and surrounding countries.

John

600,000 rows in a report? I feel sorry for the person on whose desk that lands! I think some better options include optimising the query for the reports,...

I strongly recommend that you change the Timesheet_Date column to datetime if it is in your power to do so. This will save space in your database and, more...