Search the registry on the server, this will give you a better idea of the software being used, look for 1T035G3A-91D0-45DC-8A8C-71696CE9DHBB

Have you run it to test it as looks ok to me apart from the fact that cust_id will be ambiguous in the first select and the group by. Oh,...

Who are you trying to protect the password from? I would put the username and password in the datasource for the SQL Job, it actually doesn't show in there once...

You can use xp_cmdshell, but have you had a look at Ola Hallengren's scripts, these will do all this for you, you can even set up retention period in hours.

Andy, it depends on the size of your databases, your sla's etc, but I would suggest at least once a week during a quiet time.

One thing I keep...

This will massively help me, I have a migration project for loads of databases in all different versions of sql and this will save me so much time, thank you...

Just change the set statements to select

Just a quick point, did you change the output value as well as the source value in advanced editor? If you have only set one, then it will still fail...

I'm not using it, I would never suggest to anyone to use it. I am a contractor trying to firefight issues with what others have done. They didn't even have...

The first paragraph of the link you provided said that you have to provide intent in the connection string, so guessing that's your issue.

I have done this before and set an alert, the alert fires the job, then you never need to schedule it, but I guess that depends on what your package...