THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Merrill Aldrich

Technical content about Microsoft data technologies. All opinions expressed are purely my own and do not reflect positions of my employer or associates.

Is it just me, or is this a flaw in SSMS?

This has bugged (pun?) me for some time, and I wonder if I am just nuts: I hesitate to log in to a production server with Remote Desktop and run SSMS there, preferring to do all I can with SSMS running on my local workstation instead. However, in both SSMS 2005 and 2008 there's this strange behavior when setting up an Integration Services package for SQL Server Agent: the GUI demands the package be specified using a local disk instead of a disk from the server, which of course is impossible:

  1. Open SSMS and connect to a remote server
  2. Create a new SQL Server Agent job
  3. Create a step with type SQL Server Integration Services Package
  4. Choose the File System as the source (we deploy SSIS packages as files)
  5. Click the Ellipsis (...) button
  6. I then get the rather unhelpful My Documents folder on my C: drive.

Most other server-related dialogs give you server filesystems (backup or restore, for example.) Is this just a long-overlooked bug, or am I crazy?

Published Monday, December 14, 2009 10:28 AM by merrillaldrich
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



AaronBertrand said:

Yes, but the ones that get me more riled up are the ones that offer you to browser for a folder... they look identical to others but in some cases they are missing a "Create New Folder" button.  So if you want a new folder, hit Cancel, go out to Windows Explorer, create the folder, and start over.  I complained about that inconsistency two years ago, and it was closed as "By Design"... so I guess they mean to be inconsistent and cause us unnecessary and unintuitive workflow.

December 14, 2009 1:30 PM

ALZDBA said:

- Noticed that one too. :(

- same goes for being unable to connect to a remote ssis service.

 (being member of sqladmins and server local admins and full auth on the ssis file store folder)

I hoped with sql2008 these issues would belong to the past.

December 14, 2009 2:16 PM

Tom Winter said:

We get around this by sharing the folder that contains our SSIS packages, using a $ on the share name to make it hidden and setting appropriate permissions. Then the same UNC path will work on my local machine as well as on the server.


December 15, 2009 9:21 AM

Dave Pendleton said:

I have gotten into the habit of creating the job locally, scripting it and modifying the script to run on the target server.

It only takes a minute or so longer than using the UI.

December 16, 2009 6:33 PM

merrillaldrich said:

Both good workarounds - I've been doing what Dave suggests. Still, it's frustrating!

December 16, 2009 7:50 PM

Leave a Comment


This Blog


Privacy Statement