Disconnected Edit in SSIS 2005

Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in SQL
Server 2005 Integration Services ? If so, What ?
Thanks.
In SSIS you can accomplish editing packages without a connection to the SQL
Server Several different ways.
If you are using file system deployment you can just make sure that your
development folder for the dtsx files is something different then the folder
that the agent is executing packages from.
If you are using SQL Server deployment then every package that you are
working is essentially disconnected. You have to deploy it to the sql
server using the deploy option inside of the business intelligence studio or
a package installer.
In both cases, you do not need any type of connection to the SQL server
until you deploy. You will lose some niceties that way since you cant
connect to get column or table info.
Make sense?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
Tech Blog - www.technologyis.com
*/
"DXC" <DXC@.discussions.microsoft.com> wrote in message
news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
> Is there a match for SQL Server 2000 DTS Package "Disconnected Edit" in
> SQL
> Server 2005 Integration Services ? If so, What ?
> Thanks.
|||No it doesn't. Here is why,
I imported a DTS package from a SQL Server 2000 server to 2005 Integration
services on another SQL Server 2005 computer. Regardles of where I open it,
it takes at least 20 second to scroll the horizantal bar 1 inch. I am
assuming that it is trying to check the resources/connections even though
they don't exists on the new server. This is why I thought that disconnected
edit may help to speed editing the DTS package or the SSIS package since it
has been converted..........
Thanks.
"Warren Brunk" wrote:

> In SSIS you can accomplish editing packages without a connection to the SQL
> Server Several different ways.
> If you are using file system deployment you can just make sure that your
> development folder for the dtsx files is something different then the folder
> that the agent is executing packages from.
> If you are using SQL Server deployment then every package that you are
> working is essentially disconnected. You have to deploy it to the sql
> server using the deploy option inside of the business intelligence studio or
> a package installer.
> In both cases, you do not need any type of connection to the SQL server
> until you deploy. You will lose some niceties that way since you cant
> connect to get column or table info.
> Make sense?
>
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> Tech Blog - www.technologyis.com
> */
>
> "DXC" <DXC@.discussions.microsoft.com> wrote in message
> news:32FB5B16-0012-4DD8-98CF-E52CF07BB77C@.microsoft.com...
>
>
sql