Yes, it is. I was considering this a last resort.

But it seems like the easiest.

I can add to every package.

Because I know we will soon remove the SharePoint one since...

I've tried all these items.

The stupidest part is I can immediately turn around and re-run the job and it will run to completion.

So everything is there.

So it worked successfully yesterday.

I scheduled it execute every 2 hrs.

It ran at 6pm and failed again. It didn't run after that.

So this morning I tried to run the job...

I restarted the machine and re-ran the job and it worked.

I saw this previously about the Delay Validation and updated all the packages.

I then re-imported them.

I guess SQL Server or...

I've finally finshed building my Development PC and did some preliminary testing of my permissions on my development box.

I ran into issue's as expected.

I did 4 tests

SourceDestination StatusError

ExcelOle DB Destination...

One of the items I know I am tasked to perform will be designing the backend database, creating the SSIS scripts to extract the data from existing xls and sharepoint...

Did they install BIDS on their dev systems?

The outputrowcount is fine. It returns 1

it's my identity column which is returning 0

I also tried Ident_current('dbo.jobid')

This returns the correct value

But, according to MSDN site

Be cautious about using IDENT_CURRENT to...

I tried using the OUTPUT clause but the value returned is 0

Remember, the code being executed is a SP from C#

it's called addJobId

This is where I put the OUTPUT clause

So...

It is a procedure within our database that purges out data.

The job calls this procedure.

But in AlwaysOn we have to put this job on every node

On the secondary node this...

The code needs to be able to run on non-AlwaysOn environment's

For example, existing client on SQL Server 2008 R2 who updates to our latest release

Our goal is to be able...

Actually I was able to resolve the problem.

I created a server login on my PFDB-NODE1 for RD\PFDB-NODE2$

I created a server login on my PFDB-NODE2 for RD\PFDB-NODE1$

I then did grant connect...

It turned out to be a hidden trigger that wasn't disabled during the upgrade process.

But with this composite key approach as the primary_key, if your table structure changes in the future and you need to add this additional column to the primary key this...

No. Let me explain a little more.

Let's say I'm reviewing the logs and notice we have errors migrating a patients vitals.

Normally I would find our Vitals.Migrate SPL and step...