Can somebody from the MS team help me with this? I never got an answer.
I'm a sys admin on the SQL Server and working locally. I go into bids and
try to save a copy of a dtsx file to the server (SQL Server).
I can see the folders I've defined in integration services fine, but when I
expand the folders they are empty. If I type the name of the package in, I
get the message "Package already exists, do you want to overwrite?", which I
do.
So anytime I make a change to a package and want to overwrite the one on the
server I have to select the folder and type in the package name. I just worry
at some point I will misspell a package name. Is this by design or do I have
a bug?

Thanks in advance.


Original post:

I don't think so, I'm a sysadmin on the sql server via builtin\administrators.



"Allan Mitchell" wrote:

How are you saving the dtsx package on the server? Please describe the method
you are using to deploy. There is a specific method used for deployment:
1) You deploy your project (right-click on project, then Build, after making
sure the CreateDeploymentUtility property is set to True).
2) you then run the Package Installation Wizard to place the packages on the
server. (double-click on the SSISDeploymentManifest file to do this).

From your descriptions, it does not appear that you are doing the above.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk




"sqlboy2000" wrote:

Charles,
From within BIDS I select menu File --> Save copy of package.dtsx. Then I
select my sql server as the destination. Is that not a good way to do it?


"Charles Kangai" wrote:

That should work too for individual files rather than projects. Check the
following
1) Are you saving to a named instance? (SSIS does not support named
instances; however it does not stop you from deploying although you can't
access the packages after deploying.)
2) Connect to SSIS using SQL Server Management Studio and see whether you
can see the packages from there. Be sure to select "Integration Services" in
the "Server type" drop-down of the "Connect to Server" dialog when you
connect with SQL Server Management Studio. A common mistake is to connect
with "Database Engine" in the drop-down.
3) You can also connect to the Database Engine and issue the query:
select * from msdb.dbo.sysdtspackages90. If your packages are there, you
should see them in this table if you saved them to SQL Server.

Charles Kangai, MCT, MCDBA
Author of Learning Tree's 4-day course: "SQL Server 2005 Integration
Services" http://www.learningtree.com/courses/134.htm
Author of Learning Tree's 4-day course: "SQL Server Reporting Services"
http://www.learningtree.com/courses/523.htm
email alias: charles
email domain: kangai.demon.co.uk




"sqlboy2000" wrote: