Beth's Chinese blog
Okay I admit it. I like Vista. I didn't want to like it, really. I'm a VB developer, not a gamer, not a heavy office user, I know the difference between an .exe and a .dll, I keep my own dang files organized -- I don't need the OS to index anything while taking up my precious CPU!
But.. it happened.
A month ago I got a new Lenovo T60p and after about 2 hours on Vista and Office 2007 I was hooked. Development has its bumps (it always does) but it's been a good experience so far, much better than I thought it would be.
There are a couple annoying things, however, like when I attach a SQL-Express database it coughs up an error and puts the database into read-only mode. I just have to set it back to read-write everytime. Turns out I just need to run SQL-Server Management Studio as an administrator to get around this problem.
The most annoying thing for me was that when I click on a Visual Studio Solution (.sln) file it would do nothing. Nada. Ziltch. Bummer. I was already running VS as an administrator. Today I finally decided to look around the web for a solution/hack. Here's what I found and it works great! I know a couple people in our .NET User Group were griping about this a while back. BTW, this came from the same blog as the SQL attach post above. Thanks to Bryan Phillips.
Two annoying Vista problems solved. :-)
Regarding SQL; do you have to be logged in to use it? Sounds like.
In this case IT IS AN IDIOTIC IDEA!!
It is a MAJOR security hole to work on any OS as an admin, super user etc.
If Vista doesn't let you work as a standard user throw Vista out.
Cheers
Hi Bill.
You don't run the SQL-Server service as administrator, only SSMS (SQL-Server Management Studio, the client IDE) and that's only if you need to attach/detach the databases. You can still run queries.
Cheers,
-B
What's the big problem if I'm working on my personal computer as an administrator? I don't get it!!!
There's no other users on the pc, the home lan is closed off and I can password protect anything I want to share anyway, so where's the security risk?