I have several machines. I would like the projects and solutions i create
for SQL Server (ie the nice organization of sql scripts) to be visible and
changeable from either of my machines. So, as i have a Network (mapped)
drive I copied all my solution folders over there. Then, i tried to add a
new project to a brand new solution, and tried to navigate to a mapped
network drive. I was unable to do so.

Am i missing something simple?

Thanks!

I have similar problem I think.

I am trying implement the principle of least priveledge (LUA). My developer
has a mapped drive to a location where he stores all his SQL project files
(when logged on as standard user), but when he tries to open the files in
SSMS (run as admin account) it fails. The drive is also not mapped when he
tries to open it from within SSMS

If he goes to SSMS and does file open and then maps the drive from there hen
he can access the files.

It would appear to be do with the local profiles but not sure how to change
it so that mapped drives avaialble when logged on as standard user are
available to SSMS when run as his admin account?


"Steve Schneider" wrote:

Hi,

The mapping is made by SSMS at tools install time.

Assuming you have a properly configured AD network - with your
homeDirectory attribute pointing to a valid drive and share - SSMS will
automatically use the homeDirectory as the base folder for all projects
and solutions. It's the same deal with Visual Studio, and it's the
correct way of doing it. It's also useful to have your "My Documents"
folder redirected in the same way. Check the "User Shell Folders" in HKCU.

Steve Schneider wrote:

--
Gerry Hickman (London UK)

Hi,

I don't think you need to be an a local admin to open projects from
SSMS. See post above regarding default projects location.

Barry wrote:

--
Gerry Hickman (London UK)