We're still working on this, not sure how it'll come out in the end, but a couple notes.
As a general principal, a good setup would be to do this:
1) Create a windows local group, for example, TSDataUsers. Add you and everyone else on the machine that you want to use datadude as members.
2) Logging on to SQL Server (your designdb instance) as a sysadmin role member (a local windows administrator by default, except on vista) and run the following:
CREATE LOGIN [ComputerName\TSDataUsers] FROM WINDOWS
Exec sp_addsrvrolemember 'ComputerName\TSDataUsers','dbcreator'
3) This will allow you to do the things you need to do from a project perspective, for the most part. I blogged in this earlier post:
http://blogs.msdn.com/rwaymi/archive/2006/08/18/706211.aspx
That will get you Full-text and partitioning, the other thing to consider is CLR support. If you want to use Assemblies in your project, you must configure the CLR to be usable within the designdb instance (it’s off by default).
To enable CLR, run (as an administrator):
exec sp_configure 'clr enabled', 1
reconfigure
You won’t need to be an admin from that point forward to use CLR features in the project.
This won’t address your regular windows account needs, but it will allow you to not run as a sysadmin in your sql server instance…
We're still working on this, not sure how it'll come out in the end, but a couple notes.
As a general principal, a good setup would be to do this:
1) Create a windows local
