SSIS & Azure general question

Question

I'm new to all the Azure setup, and here's my question....and what I think I'm finding out to the answer.

I can deploy SSIS-IR on Azure, and it will let me run packages.

But, I can't utilize that to develop packages?

My issue is that I'm not an administrator on my machine, which is where I have SQL installed. Thus, I can't run SSIS locally.

Is there any way I can BUILD a package without that? Doesn't seem like I can use SSMS. Can I use Visual Studio in some manner? Any extension to add for that?

I'm starting to think I have an issue (if I can't become an admin.)

Thanks!

Answer 1

I'm not really sure what Azure has to do with this but assuming you are using SSIS then you are creating a package that ultimately gets deployed (to Azure). To do that development you would be using Visual Studio locally. Assuming that when SQL was installed that the SSIS components were also installed then VS should work just fine. You don't need admin privileges to debug a package. It runs the underlying host process (DtsHost if I recall correctly).

Of course you also need to have access to the SQL server instance you are targeting (for queries) but I assume that isn't an issue here.

Answer 2

That's the kicker - SSIS is installed, but it's on my machine so I can't run it because I'm not an admin. The service is there, but need an admin account to run it.

Both the SQL Server and SSIS that I'm using initially are on my machine.

I'm SOL??

Thanks

Answer 3

OK - this is helping with part of my question. You think I should be able to do this without local SSIS service running. I haven't used these tools in a few years, so that's part of it - I don't want to waste a bunch of time figuring out something that can't be done.

I have an SSISDB configured with my Azure SSIS-IR. I can manage those. I'll look at how I should be developing something for SSIS and connectivity and just start at step 1 a little bit.

Answer 4

OK!

Thank you for your help. After resolving all the goofy issues with 32 vs 64-bit drivers & connectivity, and what's support in what version of VS, I'm working.

Why would MS release any version that doesn't support their own core technologies? And why would they develop any applications that aren't 64-bit at this point?

Oh well. Thanks for the help.