change save settings directory on SSMS 2005

when i exit sql server management studio i get the following error:

The automatically saved settings file '\\SERVER\DATA\Sql Server Management Studio\Settings\CurrentSettings-2006-09-21.vssettings' is not available for write. You can change this file on the 'Import and Export Settings' Tools Options page.

i'm guessing this might be because of the corporate policy of pointing everyone's "My Documents" at a read-only folder.

i'd like to follow the advice on the dialog but unfortunately my Tools, Options dialog does not have an 'Import and Export Settings' page.

any ideas?

This problem relates to SSMS being an offshoot of the Visual Studio Shell. I would raise a bug in Connect http://connect.microsoft.com/sqlserver|||

You could try changing the registry I found this key that might be worth looking at

HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell

|||

Probably the folder in which the vssettings file is present is a read-only location and that's why it's not allowing you to over-write it.

But you can very well re-direct your My Documents folder to any location(for which you have write access) and save the settings file will be saved when you close the SSMS.

For redirecting the My Documents folder, right click on it and select Properties and specify the new path in the Target folder location.

Hope that Helps.

Regards,

Rajesh

|||bug raised as https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=208955

change management for SQL source code

a question for you MVPs..
Is there a standard for SQL source code change management. I can do this with all my VB & .NET code using SourceSafe and a build and deploy application that validates all the source so I can deploy from a label giving me full versioning capability of my code. Is there something out there that can do the same for SQL?
regards
Mike Daviesmike
I am not a MVP as you have asked but let me give you some article to read
http://www.sql-server-performance.com/gr_change_managemenet.asp
"mike davies" <anonymous@.discussions.microsoft.com> wrote in message
news:8A57742F-51CE-4CED-8F30-091C0AC1BA60@.microsoft.com...
> a question for you MVPs...
> Is there a standard for SQL source code change management. I can do this
with all my VB & .NET code using SourceSafe and a build and deploy
application that validates all the source so I can deploy from a label
giving me full versioning capability of my code. Is there something out
there that can do the same for SQL?
> regards,
> Mike Davies|||Unfortunately there still doesn't seem to be a tool that can help me with my process. With my procedural code (VB and .NET code) there are many applications out there that give me what I want. I know there are tools that say they provide change management - but they are, are tools to show the differences between databases. How do I know the database is a reflection of my source code? I could still be deploying broken code. Sadly they are lacking and claim to be something they are not.
Doesn't anyone know of a tool that can give me the auditability of my source code that I desire.
regards,
Mark Baekdal

change management for SQL source code

a question for you MVPs...
Is there a standard for SQL source code change management. I can do this wit
h all my VB & .NET code using SourceSafe and a build and deploy application
that validates all the source so I can deploy from a label giving me full ve
rsioning capability of my c
ode. Is there something out there that can do the same for SQL?
regards,
Mike Daviesmike
I am not a MVP as you have asked but let me give you some article to read
http://www.sql-server-performance.c...managemenet.asp
"mike davies" <anonymous@.discussions.microsoft.com> wrote in message
news:8A57742F-51CE-4CED-8F30-091C0AC1BA60@.microsoft.com...
> a question for you MVPs...
> Is there a standard for SQL source code change management. I can do this
with all my VB & .NET code using SourceSafe and a build and deploy
application that validates all the source so I can deploy from a label
giving me full versioning capability of my code. Is there something out
there that can do the same for SQL?
> regards,
> Mike Davies|||Unfortunately there still doesn't seem to be a tool that can help me with my
process. With my procedural code (VB and .NET code) there are many applicat
ions out there that give me what I want. I know there are tools that say the
y provide change management
- but they are, are tools to show the differences between databases. How do
I know the database is a reflection of my source code? I could still be depl
oying broken code. Sadly they are lacking and claim to be something they are
not.
Doesn't anyone know of a tool that can give me the auditability of my source
code that I desire.
regards,
Mark Baekdal

Change Management for Jobs and DTS packages

We have a solution for change management for our databases, but how do others
handle updates/modifications to jobs or DTS packages. Does anyone know of a
tool to help us do this or is this one of those things we might have to grow
our own solution by checking out the tables in msdb?
Any suggestions would be appreciated.
Thanks,
Linda
When saving DTS packages on the SQL Server or as structured storage files
(*.dts), previous versions of the package are automatically saved. You can
go back to any previous version you wish to.
As for change management, I would suggest setting a user password so the
package can be executed by users, but not viewed or modified. Then the
package can only be altered with an owner password.
But if you want more details on changes, save your DTS packages as
structured storage files and add them to VSS (or whatever versioning
software you're using). Then you are able to capture check out and check in
details as well, and can reference change request id's etc.
Simon Worth
"lslmustang" <lslmustang@.discussions.microsoft.com> wrote in message
news:6F69B8E7-DAFA-4755-AECE-952B7A5F8142@.microsoft.com...
> We have a solution for change management for our databases, but how do
others
> handle updates/modifications to jobs or DTS packages. Does anyone know of
a
> tool to help us do this or is this one of those things we might have to
grow
> our own solution by checking out the tables in msdb?
> Any suggestions would be appreciated.
> Thanks,
> Linda
|||That's an idea we may use. What about Jobs though?
"Simon Worth" wrote:

> When saving DTS packages on the SQL Server or as structured storage files
> (*.dts), previous versions of the package are automatically saved. You can
> go back to any previous version you wish to.
> As for change management, I would suggest setting a user password so the
> package can be executed by users, but not viewed or modified. Then the
> package can only be altered with an owner password.
> But if you want more details on changes, save your DTS packages as
> structured storage files and add them to VSS (or whatever versioning
> software you're using). Then you are able to capture check out and check in
> details as well, and can reference change request id's etc.
> --
> Simon Worth
>
> "lslmustang" <lslmustang@.discussions.microsoft.com> wrote in message
> news:6F69B8E7-DAFA-4755-AECE-952B7A5F8142@.microsoft.com...
> others
> a
> grow
>
>
|||Simply script the job and keep the source script under source control
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"lslmustang" <lslmustang@.discussions.microsoft.com> wrote in message
news:1ABF1581-CF71-48A7-87AD-D047AD1BF4A1@.microsoft.com...[vbcol=seagreen]
> That's an idea we may use. What about Jobs though?
> "Simon Worth" wrote: