views:

93

answers:

3

I am running Vista and I am not using Admin user. I tried with an Admin username too, but it did not work. Any ideas?

+2  A: 

Read this blog post here for the answer to your question.

To summarize his post you need to do the following:

  1. The user needs a SQL Server login
  2. The SQL Server login needs to be a member of the build-in dbcreator role
  3. The SQL Server login needs to be a member of the build-in securityadmin role
  4. The SQL Server login needs to have the VIEW SERVER STATE privilege granted
  5. If running 2005 SP1, Grant the public group execute rights to the sp_detach_db procedure
0A0D
Ah I was about to post the same URL! Haha +1
o.k.w
@o.k.w: Quick of the draw! ;)
0A0D
Thanks. But is there any explanation as to why this is happening??
Xinxua
@Xinxua: Read this blog post here for the reasons: http://blogs.msdn.com/gertd/archive/2006/11/27/how-to-run-as-normal-user.aspx
0A0D
A: 

Check out this: Ozzie Rules Blogging

Do this:

  1. The user needs a SQL Server login
  2. The SQL Server login needs to be a member of the build-in dbcreator role
  3. The SQL Server login needs to be a member of the build-in securityadmin role
  4. The SQL Server login needs to have the VIEW SERVER STATE privilege granted
  5. If running 2005 SP1, Grant the public group execute rights to the sp_detach_db procedure
Nathan Campos
Again I am asking, is there any explanation why this is happening? Thanks for the link btw!
Xinxua
A: 

I am answering this myself. And the solution is to add the server role of "sysadmin" to "Builtin/Users" login in the SQL Server.

This should be done because the visual studio uses this user account to create a temporary database while we are editing to do design time validation.

Xinxua