Groups | Blog | Home
all groups > sql server (microsoft) > february 2007 >

sql server (microsoft) : Adding sql files to an SSIS project?


brett
2/20/2007 5:19:25 PM
I've created a new project in SSIS. I've saved the project to

c:\DBProjects\DB1

All of the sql files are located in

c:\DBProjects\DB1\sprocs

When I right click the project name and select to add existing item, I
point to the sprocs folder and add one sql file. When I look at the
folder structure, I see the sql file has been copy into

c:\DBProjects\DB1

I'd like to keep all sql files in the sprocs folder. Why does SSIS
copy them to another folder and is there a way to keep them in the
original location?

Thanks,
Brett
KenJ
2/21/2007 8:12:26 PM
Hi Brett,

SSMS keeps all the files in the same directory. I haven't found a way
to change that behavior. However, when I do want a group of files
kept in their own directory, I just add another project to the SSMS
solution (e.g., a project names sprocs). All of the files I want to
keep separate are now stored in the folder for the new project and
they are all available through the same solution in SSMS.

Thanks,

Ken

[quoted text, click to view]

brett
2/22/2007 10:08:40 AM
[quoted text, click to view]

I'm not following you. Let's say I have this stucture:

c:\Database\DB1\Stored Procedures
c:\Database\DB1\Tables
c:\Database\DB1\Functions

I want a project for DB1 that will have seperate folders corresponding
to the above folders. But as you mentioned, that can't be done. You
have to create a project for each folder than store it under the same
solution. I still can't get that to work. Here's what I do:

Add new project to solution. Point it to the "Stored Procedures"
folder and give it a name of "DB1_sprocs". I end up with this

c:\Database\DB1\Stored Procedures\DB1_sprocs

and SSIS starts moving all of the sprocs into that subfolder, which I
don't want. Can you explain how to make this work?

Thanks.

KenJ
2/22/2007 9:10:21 PM
Hi Brett,

Instead of pointing the new project to "Stored Procedures" and naming
it "DB1_sprocs" try pointing the new project to "DB1" and name the new
project "Stored Procedures" it will then put all the files for the
stored procedure project in the stored procedures folder.

Do the same for the tables and functions projects and they will map
the same way.

Thanks,

Ken



[quoted text, click to view]

brett
2/23/2007 1:33:19 PM
That works fine. But if I have multiple databases, this won't work
since each database must be a solution and only one solution can be
loaded at a time(?).

[quoted text, click to view]
KenJ
2/23/2007 6:13:56 PM
That is correct. It's an interesting limitation of SSMS. For all the
initial talk about it being based on a Visual Studio shell, it sure
lacks many of the most basic features (like adding folders to a
project).




[quoted text, click to view]

brett
2/23/2007 9:29:37 PM
Well, guess it is better than nothing. Thanks.

[quoted text, click to view]
dbahooker NO[at]SPAM hotmail.com
3/7/2007 3:04:30 PM
I'd reccomend 'learning to program' instead of relying on MS to spoon
feed you.

btw; are you that Brett Jenkins _FAGGOT_ that stole my laptop?

eat a spreadsheet; pussy

-Aaron




[quoted text, click to view]

PFC Sadr
3/7/2007 3:08:07 PM
I'd reccomend not having such a stupid first name

I mean.. Brett.. shit

let me guess. Brett Jenkins; ROFL

you should learn to program you fucking NooB and not rely on MS to
spoonfeed you

go and snort some spreadsheets; fucktard




[quoted text, click to view]

AddThis Social Bookmark Button