We are developing an ETL type data load application and we're thinking building a SSIS package to assist with this.
The application and data files to be loaded would be on the client Windows XP Workstation. The SQL Server 2005 instance would be on a networked server elsewhere.
The XP Workstation would NOT have sql server 2005.
What is the best way to handle this? Can this be achieved fairly easily?
Kevin
You’ll have to be a bit more specific on how you want to do your licensing... on a per seat basis? Per server?
No matter the model, I would highly recommend taking a read of this article on the mechanisms provided by the .NET Framework to help you implement a licensing mechanism.
|||I'm sorry I wasn't clear. I do not want to CREATE licensing for my application. I want to find out what the best, cost effective solution for me would be.Example:
Buy 1 SQL Server 2005 and call SSIS packages from the Client?
I think in this scenario I would only need 1 SQL Server Standard license?
Kevin
|||Ahh... that I’m afraid I cannot help you with much... instead I would suggest starting with the SQL Server 2005 Licensing: Frequently Asked Questions if you have not already found it.|||
If the ETL application is to be on the client then you will need to have a licensed SQL Server install there - although you need only install SSIS and tools, not the server itself.
A better - and more economical - scenario for you may be to have SSIS running on the SQL Server box. No additional license required. You can create a SQL Agent job to execute the package and invoke that job remotely from the client using T-SQL.
Either way, of course, you will have data moving over the network from client to server - and that may be a bottleneck for you.
Donald
No comments:
Post a Comment