no one? 🙁

Ive just started on the technique i described in my OP where im using manual scripts to copy the data across. Time consuming but i think it...

you need to use DBCC Shrinkfile

hmm ok, i cant remember how exactly i do it. One way you could get round it is to query the state of the job first and make sure...

Theo-929802 (7/23/2010)

---

Could you please help me with the try-catch statement?

My sp looks like this:

ALTER PROCEDURE [dbo].[usp_consolidation_user_initiate]

@jobname VARCHAR(255),

@confirmation TINYINT

AS

IF @confirmation = 0

BEGIN

SELECT 'The job did not initiate because confirmation has to...

put an output parameter varchar(200) in your sp that calls the sp_start_job procedure. Any error messages capture in a try catch loop and feed the parameter back out to...

Do you have reporting services set up? I do a funky little thing where i create a report and just put a parameter on there thats a boolean called...

ahhh yeah sorry, that was for another post i was responding too!! My bad 😛

I dont have a script that loops round multiple servers but im sure you can...

edit: wrong post 🙂

set all your instances up as linked servers. write a script to query the master database (any table). if it errors you know you have a problem somewhere...

you could do a charindex check for a blank space and make sure the number returned is greater than 0. Make sure you trim your input though incase you...

well just like any other sql jobs you can set alerts on failure, log them to the sql logs etc. I think your trying to invent something thats already...

Schadenfreude-Mei (6/17/2010)

---

oh, well that was going to be my next suggestion, profiler. If you look at the app server services you would see the service account (which wont be sa),...

I dod tend to think it cant be that bad if it can be done through ssms. Out of curiosity why are you using sa and not some sort of...

It could well be, however im not 100% sure how to check for that. The only thing i can think of is that the windows user account running the...

Check your sql error logs. There should be some messages that relate to that database being marked as suspect. Dont do anything until you have done this