Re: Cannot change installation path sql2005 (final release)

I can't see why it would affect RS. Giving permissions to the SQL Service
Account (or now in SQL2005 the SQLServer2005MSSQLUser$xxxx group) is
required if the service account is not a privileged account.

--
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

"Chris Wood" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uLFJbdg8FHA.132@xxxxxxxxxxxxxxxxxxxxxxx
>I think that the .NET Runtime message was not caused by moving the
>databases as it was there before I made the changes.
>
> It could be leftovers from removing the September CTP.
>
> Chris
>
> "Chris Wood" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:u0tKAFg8FHA.3044@xxxxxxxxxxxxxxxxxxxxxxx
>> Jasper,
>>
>> I moved msdb and tempdb on my server and got this .NET Runtime message:-
>>
>> Unable to open shim database version registry key - v2.0.50727.00000
>>
>> I did have to give permissions to an SQL2005 created user so that it
>> could read/write to tempdb and msdb in its new spot.
>>
>> Will this message be a problem for using SQL2005 with VS2005?
>>
>> Thanks
>>
>> Chris
>>
>>
>> "Jasper Smith" <jasper_smith9@xxxxxxxxxxx> wrote in message
>> news:%23Bj3KvR8FHA.2576@xxxxxxxxxxxxxxxxxxxxxxx
>>> No, it's purely a tools issue down to the shared IDE components (as far
>>> as I can work out). It should have no impact on the Engine
>>>
>>> --
>>> 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
>>>
>>> "Chris Wood" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:uYIMCpR8FHA.736@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Jasper,
>>>>
>>>> BOL explains about moving databases. If we move msdb, master etc will
>>>> this cause a problem with VS2005 interaction?
>>>>
>>>> Thanks
>>>>
>>>> Chris Wood
>>>>
>>>> "Jasper Smith" <jasper_smith9@xxxxxxxxxxx> wrote in message
>>>> news:OHDRCkR8FHA.1140@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> It's because of VS2005. Whichever you install first (SQL/VS) will
>>>>> determine the path (probably only if you install the tools but I have
>>>>> not tested that). If you install SQL first you will find you can't
>>>>> change the install path for VS2005. This is probably down to the
>>>>> shared IDE bits between the two products creating some sort of
>>>>> dependency. It's certainly not an ideal situation.
>>>>>
>>>>> --
>>>>> 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
>>>>>
>>>>> "cb" <cbenmichael@xxxxxxxxx> wrote in message
>>>>> news:1132839092.785525.126620@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>>>I am unable to change the installation path during SQL server 2005
>>>>>> tools installation. I am running out of space on my "C:" drive and
>>>>>> would like to move the SQL Server tools (and sqlExpress db
>>>>>> installation, if possible) to my "D:" drive.
>>>>>>
>>>>>> I have VS2005 on the same computer. I uninstalled the
>>>>>> SQLexpress, as part of my attempt to move all the tools
>>>>>> to my "D:" drive.
>>>>>>
>>>>>> It seems that the "native client" installation is the first to run,
>>>>>> in the standard setup, and it defines the installation path for
>>>>>> all the other installation packages.
>>>>>>
>>>>>> 1. I tried running the Native Client installation separately and was
>>>>>> unable to modify the installation path in that installation either.
>>>>>> 2. I tried a command-line installation for the native client, passing
>>>>>> a "setup.ini" file with the location property pointing to my
>>>>>> "D:" drive. This did not have any affect.
>>>>>> 3. I saw KB article that indicates that the Native Client install
>>>>>> uses
>>>>>> a pre-defined target directory
>>>>>> ("%Program Files%\Microsoft SQL Server\"). Can this be changed?
>>>>>> 4. Can I install the package in another order, installing the native
>>>>>> client last?
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages