Is my understanding correct?

[katbear]

Please forgive the basic-ness of my question, but I have only been using DTS and SSIS for 2 weeks now.

What I'd like to know is, is my understanding of SSIS package development correct.

In SQL Server 2005, I use BIDS to develop my SSIS packages. During development, I simply store my project on the local C drive.

However, once I am finished writing and testing my projects, I move them to SQL Server, using SAVE COPY AS...

Then, anytime I need to change or modify the package, I change the local file system copy of the package, then do another COPY AS... to SQL Server.

That is, once the package is on SQL Server, if you need to change it, you can only do so through BIDS, correct?

I just want to know if I'm on the right track here.

What do other people do?

Thanks much

 

[mrdenny]

Yes you on the correct track there.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[katbear]

Hi,

I guess what I am trying to determine is, what is the best solution for my particular situation.

I work for a small company, and currently I am the only one writing packages for a new 2005 server. No one else is making changes to the packages right now.

However, I need other people to be able to see the latest versions of the package that I am working on. A problem arose because no one else could see my folder due to permissions.

Should I just create a shared folder for package development? I guess it doesn't really matter where.

I get confused with all the back and forth between the file system and sql server... I just want to know what the best "system" is for what I am trying to do.

Also, some people like to keep their packages stored on the file system, other people like to deploy to sql server. I chose sql server because of all the permissions problems I was having running the packages from jobs. But there is a lot of "back and forth" involved in this. I wonder if file system deployment is easier? But I don't know how to get the packages to run from the jobs... something about passing passwords in from the command line... it seems complicated to a newbie like myself.

Thanks

 

[mrdenny]

With file system deployment you have the same issues. You still have to publish changes because the changes that you are making are on a copy stored locally on your workstation.

I would recommend getting VSS (Visual Source Safe) and use that for version control for keeping everything current and giving people a read only way to view the packages without them needing rights to the server.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com