July 5, 2012 at 9:06 pm
i know i must have BI or Visual Studio to open/modify an SSIS package but can I open a package from a client machine if I have BIS SQL 2008 on my desktop but yet the package is on a server that is SQL 2005?
July 6, 2012 at 12:53 am
You need to have the package locally. You can import it to your project in BIDS by right-clicking packages and choose Import Package. Navigate to the server and select the package. This will make a local copy of the package.
It is not possible to edit directly the package on the server, like you can with SSAS.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 6, 2012 at 7:36 am
You need to have the package locally. You can import it to your project in BIDS by right-clicking packages and choose Import Package. Navigate to the server and select the package. This will make a local copy of the package.
It is not possible to edit directly the package on the server, like you can with SSAS.
I'm confuse about one thing, you said not possible to edit directly the package on the server but if I have BIDS or Visual Studio on the server I will be able to edit it on the server correct. Is there Pros & Cons listed somewhere on editing a package on the server or on a user desktop?
July 8, 2012 at 11:58 pm
kd11 (7/6/2012)
You need to have the package locally. You can import it to your project in BIDS by right-clicking packages and choose Import Package. Navigate to the server and select the package. This will make a local copy of the package.It is not possible to edit directly the package on the server, like you can with SSAS.
I'm confuse about one thing, you said not possible to edit directly the package on the server but if I have BIDS or Visual Studio on the server I will be able to edit it on the server correct. Is there Pros & Cons listed somewhere on editing a package on the server or on a user desktop?
What I mean with not being able to edit a package on the server is that you cannot edit a package stored in SSIS without taking a local copy. That local copy can be on your user desktop or on the server itself, it doesn't matter. Usually it is a best practise not to install client software on the server, to minimize the footprint and memory usage.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 9, 2012 at 10:19 am
Also note that you cannot edit SSIS 2005 packages in BIDS/VS 2008 without upgrading them first, which will make them unusable on a SQL 2005 server.
BIDS/VS 2005 is required to edit SSIS 2005 packages. It is also a good idea to make sure you are on the same build # locally as the server, i.e. same service pack and post-SP patches.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 10, 2012 at 6:36 am
Thank you.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply