Hi guys,

My Environment:

• SQL Server 2014 Standard Edition
• SQL Server Installed on a hosted environment (different domain than our company domain)
• I have to use DNV\MyUserName when RDP in order to access the hosted environment. 
• Our Company Domain is IHM\MyUserName
• Ultimate Objective is to Execute SSIS package from a .NET application (I'm currently using MS LightSwitch)

I have the SSIS package deployed to SSISDB Catalog, I can run it locally without any problem.

Here is the script:

declare @output_execution_id bigint
exec [dbo].[CopyNewDataToLegacy] @output_execution_id output 
print @output_execution_id

If I take the same script and run it from my local machine domain(IHM\MyUserName)

I get the following error

Msg 27123, Level 16, State 1, Procedure create_execution, Line 38
The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Windows Authentication.
Msg 27123, Level 16, State 1, Procedure start_execution, Line 32
The operation cannot be started by an account that uses SQL Server Authentication. Start the operation with an account that uses Windows Authentication.

It's very clear to me that I can't execute the package without Windows Authentication.

1. Is there a workaround to execute SSIS package with SQL Server Authentication?
2. We have a secondary domain control in the hosted environment company but I can't see our IHM\Users from DNV Environment (I browsed Entire Directory from (SSMS >>> Logins >>> New Login >>> Click Search Button >>> Locations) I only see users under DNV\Users (which is not our domain)
3. I'm sure we are not the only company having this kind of issues, so I'm wondering how other companies who use hosting environment are working around this limitation.

I appreciate all the help.

Than

Given it is "different domain than our company domain" how did you point

exec [dbo].[CopyNewDataToLegacy] @output_execution_id output

to run on the remote machine?

it is not clear how you you reference the SQL account, and what is inside the stored procedure.

To me it looks like you cannot run the package unless the remote SQL server is linked.

this?

https://joethebusinessintelligenceguy.wordpress.com/2013/08/14/ssis-2012-using-sql-authentication-with-dont-save-sensitive-successfully/