Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SSIS Licensing Question Expand / Collapse
Author
Message
Posted Tuesday, December 22, 2009 2:27 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, September 29, 2010 8:14 AM
Points: 3, 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


ACap
Post #838268
Posted Tuesday, December 22, 2009 2:39 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 6:56 PM
Points: 21,620, Visits: 15,280
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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #838272
Posted Tuesday, December 22, 2009 2:50 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, September 29, 2010 8:14 AM
Points: 3, 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?


ACap
Post #838276
Posted Tuesday, December 22, 2009 2:52 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 6:56 PM
Points: 21,620, Visits: 15,280
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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #838279
Posted Tuesday, December 22, 2009 2:58 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, August 13, 2013 9:44 AM
Points: 627, Visits: 509
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....
Post #838282
Posted Tuesday, December 22, 2009 3:04 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 6:56 PM
Points: 21,620, Visits: 15,280
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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #838286
Posted Tuesday, December 22, 2009 3:19 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, August 13, 2013 9:44 AM
Points: 627, Visits: 509
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.
Post #838294
Posted Tuesday, December 22, 2009 3:33 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 6:56 PM
Points: 21,620, Visits: 15,280
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


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #838300
Posted Thursday, December 24, 2009 2:01 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Yesterday @ 7:54 PM
Points: 23,227, Visits: 31,921
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.




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)
Post #838907
Posted Friday, December 25, 2009 12:33 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Tuesday, August 13, 2013 9:44 AM
Points: 627, Visits: 509
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
Post #839123
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse