BI Development Studio Licensing in SQL Server 2005

Can someone clarify the above for me? Specifically, do you need VS
2005 installed and/or a license or is the Development Studio covered
under the SQL Server 2005 licence in it's entirety?
Thanks,
Paul2005 ships with everything you need to develop reports. Unlike 2000 where
you had to have VS 2003. If you have VS 2005 it will integrate with it
(essentially they are shipping a special version of VS with RS 2005).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<penfoldtaylor@.gmail.com> wrote in message
news:1129804746.927756.59790@.g49g2000cwa.googlegroups.com...
> Can someone clarify the above for me? Specifically, do you need VS
> 2005 installed and/or a license or is the Development Studio covered
> under the SQL Server 2005 licence in it's entirety?
> Thanks,
> Paul
>|||Thanks for the clarification. As an aside, am I right in saying that
the 2005 Business Intelligence Development Studio is incompatible with
MS Report Services Server 2000?|||It will convert 2000 reports to 2005 formats but you cannot use 2000 server
with 2005. You can upgrade RS 2000 to RS 2005 without upgrading SQL Server
to 2005. This means that the database engine can still be 2000 and when you
upgrade RS 2000 to 2005 the object/metadata store gets updated. You still
need a 2005 license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<penfoldtaylor@.gmail.com> wrote in message
news:1130413198.173467.275250@.g49g2000cwa.googlegroups.com...
> Thanks for the clarification. As an aside, am I right in saying that
> the 2005 Business Intelligence Development Studio is incompatible with
> MS Report Services Server 2000?
>

Best way to handle License issues

Here is the scenario:

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