Is there an alternative to run "SSIS like" process on remote client server without a full SQL Server install?
We are working on a project that will allow remote clients to pull data from legacy databases into a SQL express table that we will consume via a web service. There will be some data transformation that needs to take place in the import process. In the past I have simply used SSIS for this type of task, however, since this is in a client environment that may be duplicated 100 times, the cost of implementing full SQL servers in every remote site is killing us. I would like to simply install SQL Express, and use some other method of getting the data from the legacy databases into our SQL tables. Is there any good alternatives? How is PowerShell at doing pivot or sync operations? Is PowerShell too slow to handle as many as a few thousand records? Is there a way to perform SSIS functionality in a custom C# application without writing LOTS of code? I wish there was an SSIS runtime...
ASKER
Thanks Pedro, but the problem is that we have no guarentee that our remote clients will even have a SQL install that has SSIS (ie. SQL Server 2008 Standard or above). Also, it is our policy not to install our applications on Client Servers. What we are trying to avoid is purchasing a full SQL server license at each remote site. What our ideal package would consist of ideally is a) a Windows Web Server 2008 server, b) a web service, c) a SQL Express database(s) and d) a solution to sync data from various legacy datbases to our own proprietay SQL express table.
I never tried, but you already tried to call a SQL job on the server through the SQL Express clients?
or call a stored procedure
ASKER
Stored proceedures will work when we are talking to other SQL Server databases, but may not be very usefull when we need to import data from MySQL or Oracle, etc. I think we are going to have to setup our own SQL server with SQL Standard, but wanted to see if anyone had any better ideas before we take on the cost of doing so. Thanks!
When I told you to use stored procedure is only to call the SSIS package not import and do all the work inside it. You can call a stored procedure remotly in each client and the stored procedure in the server could call the SSIS package... understood!?
regards,
Pedro
regards,
Pedro
ASKER
But my question was to use something other than SSIS, because we don't know if SSIS will be installed at the client end, and it we used SQL Express, SSIS in not included with that... So it is impossible to call a SSIS package using any method if SSIS is not installed. What I was looking for was an alternative to SSIS. Sorry for the miscommunication.
Brad
Brad
Sorry... but you dont understand what i wrote...
YOU DONT NEED SSIS IN THE CLIENT if you have a stored procedure in the server that call the SSIS package located in the server... what you need it's just call this stored procedute from each client using SQL express!!!
YOU DONT NEED SSIS IN THE CLIENT if you have a stored procedure in the server that call the SSIS package located in the server... what you need it's just call this stored procedute from each client using SQL express!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
very good... The SSIS is included with SQL... Install only on the server...
I hope I helped you!
If you dont have more issues related to this subject, just set this question as answered.
Always welcome.
regards,
Pedro
I hope I helped you!
If you dont have more issues related to this subject, just set this question as answered.
Always welcome.
regards,
Pedro
Helped?
regards,
Pedro