Hi ssexton.

I think I probably have some bad news for you about launching an SSIS Package from Access.

I'm using Access2003, so it may be different, but from my experience, security...

Hi Gino.

I think a better thing to say than that the 32-bit property only applies at design time is to say that it obviously only applies in that interface.

If you...

It depends on what you're doing.

In the first case, I was creating a package that output CSV files. This SSIS Package did not fail to execute properly from...

Yes Regan, if SSIS is not invoked directly from the job, then 64-bit probably doesn't crash.

Either that, or you're invoking the 32-bit .exe from the agent/task you call.

Of course...

Thanks John.

I had a sinking feeling the answer was going to be something like that...

It's like Microsoft ran out of time and went, "Oh well, we just won't finish the...

Yes, was missing the dot between sys and servers.

All is good now, and my code is working fine.

No more pesky dropped servers and resulting problems.

Hi again Lowell.

Where does sysservers exist? In msdb? I can't seem to find it.

Thanks a billion for that Lowell. Exactly what I was looking for. Now I can get on with things.

Well, that's exactly what I did.

I took the role granted to all the users (and for testing purposes, for the role I have too, which is a bit more admin)...

Thanks for the interesting article.

I think you're suggesting there I could use check constraints to disallow Deletes and Updates on the table. And if I just didn't do the...

That's my exact problem at the moment too.

I'm calling one from a job, but I hadn't first considered that the SP will be called in a Windows Authentication Mode only...

But if the account being called by the sp is whatever the default SQL Agent account is, then as you point out, I have to change the default SQL Agent...

Ok, there is clearly something I'm still not understanding then.

The current agent is set to Administrator. This is the administrator account for the Windows Domain.

When I login as this...

Oh, right. I do see what you're saying. You're saying that if I switch the user that executes agent tasks to something that requires a lower permission level, so...

The Windows Authentication Administrator account, which is the one you are referring to, already does have SQLAgent permissions, and runs fine if you are logged onto the server as that...