May 9, 2010 at 8:45 am
Sorry, got busy for the day. Perry is correct. To import data, you just need insert (maybe update/delete) on tables. To export, just SELECT.
Backups are the easiest way to move all data. If you aren't moving everything, then I might suggest the Import/Export wizard, which just needs those permissions.
However data movement isn't simple if you're not moving everything in a table. If you make partial moves, you have to deal with merges. If you have PK/FKs defined (and you should), it gets more complicated.
I'd suggest that you sit with them and define what it is specifically they want to do. "Moving data" isn't specific enough, and it will result not only in more rights than they need, but also a slack/ lazy attittude that will flow through development. People might write code that exceeds the privileges they need, maybe even doing things like shelling out. You'll have issues with testing if data is flowing in and out and you aren't keeping track, and the developers will likely start to think they can just much with production if they want to, changing data or code.
May 10, 2010 at 7:57 am
in my experience people always elevate privileges in a vain attempt to make things work, rather than sit down and work out what is required!!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 10, 2010 at 10:05 am
Thanks Guys
appeciate all the input
i guess i need to find out exactly what the developer's requirment(s) are
the sysadmin just came in and asked me what permissions developers need to do their own exports.
i need to get more on this i guess
Jim
May 10, 2010 at 11:57 am
Hi Folks
here is what I have been told by the sysadmin for the developers
apparently
they are not talking about sql server database exports and imports
these devlopers are using some SHAREPOINT utility (STSADM) that:
Exports site and subsite data from your Microsoft Office SharePoint Server 2007 installation.
Imports site and subsite data from your Microsoft Office SharePoint Server 2007 installation.
http://technet.microsoft.com/en-us/library/cc262465.aspx
http://technet.microsoft.com/en-us/library/cc263431.aspx
They say that it requires the dbo privilege in order for it to work
Does anyone have any experience with this SHAREPOINT utility and whether or not they do need dbo privilege ?
Thanks
Jim
May 11, 2010 at 3:54 am
ah that explains things. There are a few issues with STSADM not the least the restriction on the site size. If the site is larger than 10-15 GB you may see issues.
Backup and restore through Central Administration as the Sharepoint service accounts already have the necessary access to all components!
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
May 11, 2010 at 9:21 am
Hi Perry
these devlopers are using thier own active directory domain accounts
from what articles i have read, it seems to use\ STSADM you need db_owner, dbcreator, and securityadmin
Thanks
Jim
May 11, 2010 at 3:59 pm
FYI
seems they only needed db_owner role but
problem was that there are three databases that needed the role as they only had it on one of the databases:
Databases needing db_owner:
SharePoint_AdminContent_...
..._SharePoint_Config
..._WSS_Content_MySite
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply