|
|
Posted by Dan Guzman on 03/05/07 13:00
I agree UAC can be annoying on a development box but I've been running Vista
with UAC and haven't had to resort to turning it off. I need to run VS as
administrator. It's optional with SSMS depending on the features I use
(e.g. stop/start services requires admin).
--
Hope this helps.
Dan Guzman
SQL Server MVP
<theintrepidfox@hotmail.com> wrote in message
news:1173031039.763449.115250@n33g2000cwc.googlegroups.com...
> On 1 Mar, 22:13, Erland Sommarskog <esq...@sommarskog.se> wrote:
>> (theintrepid...@hotmail.com) writes:
>> > Found the Solution on Vista:
>>
>> > - Go to Control Panel and Switch to Classic View
>> > - Click on User Accounts
>> > - Click on Turn User Account Control on or off
>> > - Uncheck use User Account Control (UAC) to help protect your
>> > computer.
>> > - OK
>> > - Restart System
>>
>> > Try again to attach the DB. It should work now.
>>
>> > Hope this helps anyone else having this problem.
>>
>> Maybe a bit heavy-duty. The point with UAC in Vista as I understand it,
>> is that you should not run as Administrator all the time, only when you
>> need it. While running as Administrator is convenient, it makes it
>> easier for any infections your machines may catch to spread. I think
>> there is a context-menu option "Run As Administrator".
>>
>> Personally, I have not had any encounter with Vista yet.
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se
>>
>> Books Online for SQL Server 2005
>> athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
>> Books Online for SQL Server 2000
>> athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
> Hi Erland
>
> Correct. It's heavy duty and my first attempt was to right-click on
> the Management Studio Icon and to choose the 'Run As Administrator'
> option which didn't work.
> UAC is indeed a good feature and helps to protect. But following this
> process didn't solve the problem and there was no other choice than
> having to turn off UAC.
> I haven't tried turning UAC on since I attached the databases to see
> what its effect is.
>
> To put it short, UAC is good but not in a development environemnt.
> Despite having turned it off VS 2005 still warns me that it may not
> work correctly, needing Admin rights but it starts fine without any
> errors so far. And anyway, what's the REAL risk of having it turned
> off. A Vista machine with UAC off won't become less protected than a
> XP machine used to be and any additional security software and common
> user sense will help protect the same way. I reckon it's rather good
> for my dad who clicks on and executes everything he's prompted with.
> Bless him and his viruses.
>
> If anyone has a better suggestion to this workaround which will work
> with UAC on, please post it here.
>
> All the best,
>
> Martin
> Invent2b Group
>
Navigation:
[Reply to this message]
|