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 ««123»»

SSIS needed to run SSIS jobs? Expand / Collapse
Author
Message
Posted Sunday, September 29, 2013 1:20 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 11:28 AM
Points: 13,641, Visits: 11,517
dan-572483 (9/28/2013)
By "install SSIS" I mean the Integration Services checkbox in Setup.

So it sounds like it doesn't need to be on installed on the Database Engine server if a package is being run from a client machine that has SSIS installed and is connecting to the server.

What if you want to schedule a data import package in SQLAgent. Do you need to run Setup on the server with the Integration Services box checked in that case?


Yes. You need to install Integrations Services on every machine that will run a SSIS package.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1499764
Posted Thursday, October 17, 2013 12:58 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 10:51 AM
Points: 558, Visits: 1,652
Koen,

I'm a little farther into this project, but I'm still confused. In the blog post you linked to earlier, you wrote


You only need to install Integration Services when you want a dedicated SSIS server, but you’ll need to store your packages on the file system.


And here's where I'm at now. I wrote a package on my workstation where BIDS is installed that combines data from a text file and an access file and imports it successfully into a table in a SQL database. From what read I should be able to copy the dtsx file to a SQL Server that was installed without Integration Services checked and run the dtsx file via a SQL Agent job.

After giving the SQL Agent account access to the folder with the dtsx, text and MDB files, then checking the "Use 32 but runtime" it reports failer, but now the error message reads


To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher. End Error DTExec: The package execution returned DTSER_FAILURE (1).


But when I do a select on the table, I see that the data rows from the text file were imported, but the Access data was not. Now I'm thinking is is an issue of recent 64-bit versions of SQL not playing will with older version Access files, which I've wrestled with before.

Do you think the solution is

1) Run SQL setup on the Server and check Integration Services (This is a failover cluster and I've read wornings from microsoft about this)?

2) Dig deeper into the 64-bit SQL 2008/Access 2003 file issues?

3) Run the dtsx package from SQL Agent on a 32-bit installation of SQL Server, tageting the 64-but instance where the database lives?
Post #1505877
Posted Thursday, October 17, 2013 2:35 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
I think that the Conclusion in Koen's blog needs a bit of a tweak. Perhaps something like this?

Only when you want to set up a dedicated SSIS Server will you need to install Integration Services on its own, and if you do this you’ll need to store your packages on the file system.


If you read the sections above the conclusion, you'll see that the packages were executed successfully (using dtexec) only when the Integration Services checkbox was ticked during installation.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1505906
Posted Friday, October 18, 2013 1:17 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 11:28 AM
Points: 13,641, Visits: 11,517
dan-572483 (10/17/2013)

And here's where I'm at now. I wrote a package on my workstation where BIDS is installed that combines data from a text file and an access file and imports it successfully into a table in a SQL database. From what read I should be able to copy the dtsx file to a SQL Server that was installed without Integration Services checked and run the dtsx file via a SQL Agent job.

After giving the SQL Agent account access to the folder with the dtsx, text and MDB files, then checking the "Use 32 but runtime" it reports failer, but now the error message reads


To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher. End Error DTExec: The package execution returned DTSER_FAILURE (1).


But when I do a select on the table, I see that the data rows from the text file were imported, but the Access data was not. Now I'm thinking is is an issue of recent 64-bit versions of SQL not playing will with older version Access files, which I've wrestled with before.

Do you think the solution is

1) Run SQL setup on the Server and check Integration Services (This is a failover cluster and I've read wornings from microsoft about this)?

2) Dig deeper into the 64-bit SQL 2008/Access 2003 file issues?

3) Run the dtsx package from SQL Agent on a 32-bit installation of SQL Server, tageting the 64-but instance where the database lives?


Phil is right, the conclusion of my blog post could have been worded better. You definately need to install SSIS, but not necessarily SQL Server.
Regarding Access: which provider are you using? JET OLEDB or ACE OLEDB? JET is only available in 32-bit, but ACE has also 64-bit providers available.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1506002
Posted Friday, October 18, 2013 1:17 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 11:28 AM
Points: 13,641, Visits: 11,517
Phil Parkin (10/17/2013)
I think that the Conclusion in Koen's blog needs a bit of a tweak. Perhaps something like this?

Only when you want to set up a dedicated SSIS Server will you need to install Integration Services on its own, and if you do this you’ll need to store your packages on the file system.


If you read the sections above the conclusion, you'll see that the packages were executed successfully (using dtexec) only when the Integration Services checkbox was ticked during installation.


Thanks. I adjusted the blog post with your suggestion.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1506003
Posted Friday, October 18, 2013 9:57 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 10:51 AM
Points: 558, Visits: 1,652
Koen Verbeeck (10/18/2013)
[quote]dan-572483 (10/17/2013)

Regarding Access: which provider are you using? JET OLEDB or ACE OLEDB? JET is only available in 32-bit, but ACE has also 64-bit providers available.


The package was designed on a 32-bit machine - from which the package works - and I'm trying to run it on a 64-bit server with 64-bit SQL. Does this mean I need a 64-bit machine with BIDS installed to edit the package?
Post #1506249
Posted Friday, October 18, 2013 10:23 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
dan-572483 (10/18/2013)
Koen Verbeeck (10/18/2013)
[quote]dan-572483 (10/17/2013)

Regarding Access: which provider are you using? JET OLEDB or ACE OLEDB? JET is only available in 32-bit, but ACE has also 64-bit providers available.


The package was designed on a 32-bit machine - from which the package works - and I'm trying to run it on a 64-bit server with 64-bit SQL. Does this mean I need a 64-bit machine with BIDS installed to edit the package?


Packages are the same regardless of the number of 'bits'. But you can run them in either 32- or 64-bit mode (if your server is 64-bit) - according to requirements.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1506261
Posted Monday, October 21, 2013 2:06 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 10:51 AM
Points: 558, Visits: 1,652
I swtiched from the Jet provider to the ACE Access 10.0 provider, but I'm havng the same result: The data from the text source file successully imports, but the Access data does not, and the Job History Log reads: "To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher."

So it looks like the integration services check on setup is required to use an Access source but not text?
Post #1506862
Posted Monday, October 21, 2013 2:10 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 5,317, Visits: 12,355
dan-572483 (10/21/2013)
I swtiched from the Jet provider to the ACE Access 10.0 provider, but I'm havng the same result: The data from the text source file successully imports, but the Access data does not, and the Job History Log reads: "To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher."

So it looks like the integration services check on setup is required to use an Access source but not text?


You seem extremely averse to performing the SSIS installation. What is the problem?



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1506863
Posted Monday, October 21, 2013 2:23 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: 2 days ago @ 10:51 AM
Points: 558, Visits: 1,652
I was planning to install Integration services during the last downtime when I can across this:
http://technet.microsoft.com/en-us/library/ms345193(v=sql.105).aspx

But from what I'm gathering, there's no need to configure integration services service as a clustered service unless I need to use functionality beyond what SQLAgent can do.

So I can install this on both nodes, get the ability to run packages on the server using SQLAgent, leave IS service off and not worry about cluster-related issues with IS?
Post #1506871
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse