December 1, 2014 at 11:39 am
psc032802 (12/1/2014)
the end users in this scenario are people wanting to run the data profiling features. my original question was what needs to be installed and where does it need to be installed in order for this to be possible?1. does SSIS need to be installed on the server machine housing the database?
That depends. Is this the server which will be housing the packages and running the packages? If so, yes. If not, no. But SSIS will need to be installed on the box that does run the packages.
2. does SSIS need to be installed on the individual client machines wanting to run these functions?
Depends on what you mean by data profiling features. If you have people building SSIS packages on their local boxes, then by all means install it. If, however, they have permissions on the package-running server to run the packages, then no. They do not need this local to their machines.
December 2, 2014 at 3:32 am
Just to clarify:
Integration services needs to be installed on one sql server where the packages will be run
That integration services can connect to databases on other sql servers or to flat files, excel, other types of database etc. via OLEDB, ODBC or ADO.net connections
The person(s) who create packages will need a copy of the BIDS tools (SQL Server Client Tools) which is installed from the sql server installation media. This must be the same version as the integration services version on the server - packages created with BIDS 2008 will not work on a SQL 2005 server and so on. Whether you choose to put BIDS on a server or a user's pc is up to you but consider the workload on the server. We always have BIDS on user pc.
Once a package is created and tested it can be deployed to msdb on the integration services server or can be run from a fileshare location. SQL agent jobs are the usual way of running packages by selecting SSIS Package as the type in the jobstep then completing the details and setting a schedule.
Developing packages is a full skillset in itself and not for end users. I'd recommend going on a course if possible or at least some serious reading such as the stairway series on this site.
December 2, 2014 at 12:30 pm
if the packages are to be run against a single database/server, then it would be best to install ssis on that same machine, correct?
then bids/ssis needs to be installed locally on the computers of people wanting to trigger the packages. in my case, the some of the tasks.
December 2, 2014 at 12:37 pm
psc032802 (12/2/2014)
if the packages are to be run against a single database/server, then it would be best to install ssis on that same machine, correct?then bids/ssis needs to be installed locally on the computers of people wanting to trigger the packages. in my case, the some of the tasks.
I think we need to take a step back and start from the beginning.
Who built your SQL Server system? What is your position / job title? How much experience do you have with SQL Server?
December 3, 2014 at 2:57 am
No, BIDS only needs to be installed for people creating packages. You can run them in various ways such as from sql agent or from command line dtutil or as has been done by one of our developers, by writing a web page for the users which calls a stored procedure which starts a sql agent job to import their data.
The procedure contains: EXEC msdb.dbo.sp_start_job N'Import Order' - it works but I'm not sure if it's the best way.
December 3, 2014 at 4:00 am
Brandie Tarvin (12/2/2014)
psc032802 (12/2/2014)
if the packages are to be run against a single database/server, then it would be best to install ssis on that same machine, correct?then bids/ssis needs to be installed locally on the computers of people wanting to trigger the packages. in my case, the some of the tasks.
I think we need to take a step back and start from the beginning.
Who built your SQL Server system? What is your position / job title? How much experience do you have with SQL Server?
FYI: I am asking these questions so we have a better idea of exactly what information we need to give you. So please do answer them so we can tailor our answers more appropriately.
December 3, 2014 at 9:06 am
i have a similiar question: i have SSMS 2008r2. Our database server has SSIS installed. I want to view the packages. Do i need to install SSIS on my machine?
December 3, 2014 at 9:14 am
Have people stopped taking time to learn the technology they want to use before trying to use it?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
December 3, 2014 at 9:23 am
jliu 81028 (12/3/2014)
i have a similiar question: i have SSMS 2008r2. Our database server has SSIS installed. I want to view the packages. Do i need to install SSIS on my machine?
No. Just BIDS or Visual Studio with the BIDS addons.
December 3, 2014 at 9:26 am
thank you. before i ask my dba to install BIDS on my machine, is there any free version that i can play around first?
December 3, 2014 at 9:31 am
i used to be able to use DTS to transfer data from source to destination in sql 2000. now we upgraded to sql 2008r2, my previlige is deprived. refreshing my test db from production requires a ticket. huh.
December 3, 2014 at 9:39 am
jliu 81028 (12/3/2014)
thank you. before i ask my dba to install BIDS on my machine, is there any free version that i can play around first?
BIDS is part of the SQL Server install. Up to a certain point, there are are no SQL Server eval versions (except for 2014). I don't recommend using a version of BIDS different from your SQL Server because you'll either A) Be unable to read the package because the package was made with a later version than the BIDS you have or B) Upgrade the package which may prevent some components of it from acting properly while you're looking at it.
Plus an upgraded package won't work with your version of SQL Server if you push it back up to the server.
That said, the only eval version of SQL Server I know of is SQL 2014. And enough has changed between that and SQL 2008 that I wouldn't trust the 2014 Visual Studio with my 2008 package if I were brand new to learning SQL Server and wanted to know how 2008 things worked.
December 3, 2014 at 9:41 am
jliu 81028 (12/3/2014)
i used to be able to use DTS to transfer data from source to destination in sql 2000. now we upgraded to sql 2008r2, my previlige is deprived. refreshing my test db from production requires a ticket. huh.
Umm, not sure what this means, but it sounds like an internal security issue. DTS Import / Export Wizard still works fine in 2k8 R2.
December 3, 2014 at 9:42 am
I am not a DBA. Not a developer either. More of an end user of the data typically analyzing it.
I'm mostly interested in the data profile task in order to find out more about the data itself. I do not care about its etl capabilities, error logging, real time monitoring, etc. I just want to be able to run the data profile task so I can get my hands on the information it produces.
Brandie Tarvin (12/2/2014)
psc032802 (12/2/2014)
if the packages are to be run against a single database/server, then it would be best to install ssis on that same machine, correct?then bids/ssis needs to be installed locally on the computers of people wanting to trigger the packages. in my case, the some of the tasks.
I think we need to take a step back and start from the beginning.
Who built your SQL Server system? What is your position / job title? How much experience do you have with SQL Server?
December 3, 2014 at 9:45 am
thanks for replying me again. if I ask my dba to install BIDS on machine, what do you think he'll be concerned about? security? my skill/knowledge of SSIS?
Viewing 15 posts - 16 through 30 (of 41 total)
You must be logged in to reply to this topic. Login to reply