I agree, I never had a need to open 100 connections like that and probably never will.

If you are trying to connect over Kerberos, you need to have your Domain Admin to do a "SETSPN" to register the Service Principal Name.

These are all valid methods that I would use.

Personally have each package in seperate job steps in order, if a step fails then fail the job.

I used to do this before we had 2K5 and above! The additional things we did was to have the tables in different files\filegroups on difference drives for better...

I had a similar experience with a 3rd party app db and the vendor support team did nothing to help the situation. Lucky enough the code was in a stored...

It was stated earlier that you can not recover a password only reset it, whether or not you migrate the logon from any SQL Server version.

Deepak are you from Cleveland?

Have you try this code???

Exactly what I would do...

I believe you need the Backward Compatible Components installed!

I agree along with Gail... ➡

I think it would if useful to also add the client_tcp_port from the connections DMV, because your SQL Server should only be using 1 open port? :w00t:

For newbies like yourself you can start off by using a Maintenance Plan!:w00t:

For a job change there NO reason for a restart!

Some things to look at also:

1. What protocols are you using, I tend to shut everything down except TCPIP.

2. Make sure your Service Principal Name is set correctly, ask you...