SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS Licensing Question


SSIS Licensing Question

Author
Message
acapucion
acapucion
SSC-Enthusiastic
SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)

Group: General Forum Members
Points: 101 Visits: 169
I have a scenario, installed SQL Server 2008 Database Engine and SSIS component into one server.

Developer wanted to have capability to design SSIS, so I installed him BIDS (Business Intelligence Development Stuido)

When the developer tried to design/create new SSIS project it gives an error that SISS service must be installed?

If decided to install does it requires license? or is there licenses issue on this.

Please advise.

Nodcap

ACapHehe
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)

Group: General Forum Members
Points: 131778 Visits: 18634
acapucion (12/22/2009)
I have a scenario, installed SQL Server 2008 Database Engine and SSIS component into one server.

Developer wanted to have capability to design SSIS, so I installed him BIDS (Business Intelligence Development Stuido)

When the developer tried to design/create new SSIS project it gives an error that SISS service must be installed?

If decided to install does it requires license? or is there licenses issue on this.

Please advise.

Nodcap


If it is installed on a development machine that has SQL server already running - you should be covered by licensing - so long as that machine does not provide production services.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

acapucion
acapucion
SSC-Enthusiastic
SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)

Group: General Forum Members
Points: 101 Visits: 169
what if does not have the sql server, only SSMS and BIDS without SQL Server Developer Database Engine?
Means it will require license?

ACapHehe
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)

Group: General Forum Members
Points: 131778 Visits: 18634
acapucion (12/22/2009)
what if does not have the sql server, only SSMS and BIDS without SQL Server Developer Database Engine?
Means it will require license?


You will still need to install the SSIS services onto a dev machine - and you should be covered - again with the same caveat that the system does not house any production services.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

SSIS\SSRS\SSAS
SSIS\SSRS\SSAS
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3064 Visits: 575
CriquedeSQL... I think you missunderstood the question above. I think he is saying that he installed SQL 2008 and SSIS on one server (let it be a DEV box). Then he installed a SQL server clinet tools and BIDS in his developer local machine. COrrect me if i am wrong here.

If i am not wrong then..you still have to enable your IIS to run and build SSIS packages and also SSIS services at local machine should be running too. Now I cannot verify that since I do have a SQL engine installed locally to my machine.

I do a lot of ssis too.

I usually ask for remote desktop connection and log to dev box and build my ssis packages in that dev box rather than my local machine. This way it helps me a lot of trouble during my own test and build.

Let say If I build a ssis locally in my local machine then the drive and folder strcuture would be different than the DEV machine. SO I have to modify many things before even i test it on my own. COnnection issue and Path issue....
This is just my thought....
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)

Group: General Forum Members
Points: 131778 Visits: 18634
Gkhadka (12/22/2009)
CriquedeSQL... I think you missunderstood the question above. I think he is saying that he installed SQL 2008 and SSIS on one server (let it be a DEV box). Then he installed a SQL server clinet tools and BIDS in his developer local machine. COrrect me if i am wrong here.

If i am not wrong then..you still have to enable your IIS to run and build SSIS packages and also SSIS services at local machine should be running too. Now I cannot verify that since I do have a SQL engine installed locally to my machine.

I do a lot of ssis too.

I usually ask for remote desktop connection and log to dev box and build my ssis packages in that dev box rather than my local machine. This way it helps me a lot of trouble during my own test and build.

Let say If I build a ssis locally in my local machine then the drive and folder strcuture would be different than the DEV machine. SO I have to modify many things before even i test it on my own. COnnection issue and Path issue....
This is just my thought....


The question was:
If decided to install does it requires license? or is there licenses issue on this.

For that question, the answer is as it was stated - if he decides to install SSIS on the DEV machine, he will not need a license unless production services are being housed from that box.

If i am not wrong then..you still have to enable your IIS to run and build SSIS packages and also SSIS services at local machine should be running too. Now I cannot verify that since I do have a SQL engine installed locally to my machine.

I run SSIS services on my dev box and do not install/disable IIS - IIS is not required to build SSIS packages.
As a matter of preference - I prefer to have SSIS installed on the box from which I am developing packages.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

SSIS\SSRS\SSAS
SSIS\SSRS\SSAS
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3064 Visits: 575
Yes.....you are right, if he already have installed SQL 2008, then there is no need for new liscense for SSIS. SSIS comes with SQL.

I think the main concern for him that his developer is not able to build/design ssis packages through his local machine.

If I were you than I would reinstall the SQL CLient tools and SSIS service agian in developer local machine. I am thinking that something went wrong during the installing process.

You still have to have SSIS service running locally (in developer local box) to build and design ssis packages. Installing just BIDS is, i think, not enough. Correct me here someone if a I am wrong.
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)SSC Guru (131K reputation)

Group: General Forum Members
Points: 131778 Visits: 18634
Gkhadka (12/22/2009)
Yes.....you are right, if he already have installed SQL 2008, then there is no need for new liscense for SSIS. SSIS comes with SQL.

I think the main concern for him that his developer is not able to build/design ssis packages through his local machine.

If I were you than I would reinstall the SQL CLient tools and SSIS service agian in developer local machine. I am thinking that something went wrong during the installing process.

You still have to have SSIS service running locally (in developer local box) to build and design ssis packages. Installing just BIDS is, i think, not enough. Correct me here someone if a I am wrong.


For troubleshooting the SSIS error - we need more detailed information.

To run BIDS and develop SSIS packages - the local SSIS service does not need to be running - just verified by testing the creation of a new package.

acapucion - please provide detailed info concerning the error message if you would like that issue discussed.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Lynn Pettis
Lynn Pettis
SSC Guru
SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)SSC Guru (202K reputation)

Group: General Forum Members
Points: 202328 Visits: 40027
Gkhadka (12/22/2009)
CriquedeSQL... I think you missunderstood the question above. I think he is saying that he installed SQL 2008 and SSIS on one server (let it be a DEV box). Then he installed a SQL server clinet tools and BIDS in his developer local machine. COrrect me if i am wrong here.

If i am not wrong then..you still have to enable your IIS to run and build SSIS packages and also SSIS services at local machine should be running too. Now I cannot verify that since I do have a SQL engine installed locally to my machine.

I do a lot of ssis too.

I usually ask for remote desktop connection and log to dev box and build my ssis packages in that dev box rather than my local machine. This way it helps me a lot of trouble during my own test and build.

Let say If I build a ssis locally in my local machine then the drive and folder strcuture would be different than the DEV machine. SO I have to modify many things before even i test it on my own. COnnection issue and Path issue....
This is just my thought....


You wouldn't want to work for me. There should be almost no reason for any developer to remote connect to a server for development purposes (I happen to have one package that requires this since the SFTP software used does not work with UNC's). There are only two admin remote terminal services connects available unless you are also running terminal services on the server.

Using the robust dynamic configuration capabilities of SSIS, you should easily be able to create/test/debug your SSIS packages locally and then deploy them to a development server for integration testing, a QA/UAT server for acceptance testing, and then finally to a production server for actual work. The only thing that would have to change is the configuration file(s) that define source and destination paths/locations.

Cool
Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
SSIS\SSRS\SSAS
SSIS\SSRS\SSAS
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3064 Visits: 575
Don't worry Lynn.....i don't think I will ever work for u ....................Anyway it was nice knowing that there could be several reasons that building SSIS packgaes at local machine might not be possible and feasible in some instances...and you mentioned one of the reasons, and there are few more.....( and there are few more..........but i bet you u know that all...after all u seems to have a whole lot about SSIS) and same thing happen to me...............
I am not saying you cannot build and test SSIS in your local machine rather doing than remote desktop connection. I am just saying it is more easy for me. When you are working with over 100 SSIS packages - even changing Drive name, folder strcture, copying data files, locally and loading millions rows just for test and config file is just waste of time and resources for me. Common it's just a dev machine.....it's where I exercise my possibilities.......I should not be bound by any sort of restrctions other than company ploicy...
Well, let's focus here on the real issue and help him solve the problem...
Merry X-mas
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search