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:
- The user needs a SQL Server login
- The SQL Server login needs to be a member of the build-in dbcreator role
- The SQL Server login needs to be a member of the build-in securityadmin role
- The SQL Server login needs to have the VIEW SERVER STATE privilege granted
- If running 2005 SP1, Grant the public group execute rights to the sp_detach_db procedure
0A0D
2009-11-30 14:23:29
Ah I was about to post the same URL! Haha +1
o.k.w
2009-11-30 14:24:06
@o.k.w: Quick of the draw! ;)
0A0D
2009-11-30 14:25:28
Thanks. But is there any explanation as to why this is happening??
Xinxua
2009-11-30 14:36:27
@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
2009-11-30 14:56:48
A:
Check out this: Ozzie Rules Blogging
Do this:
- The user needs a SQL Server login
- The SQL Server login needs to be a member of the build-in dbcreator role
- The SQL Server login needs to be a member of the build-in securityadmin role
- The SQL Server login needs to have the VIEW SERVER STATE privilege granted
- If running 2005 SP1, Grant the public group execute rights to the sp_detach_db procedure
Nathan Campos
2009-11-30 14:23:51
Again I am asking, is there any explanation why this is happening? Thanks for the link btw!
Xinxua
2009-11-30 14:37:20
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
2009-12-14 11:54:47