Accessing databases using integrated security from Sharepoint.
When creating custom webparts or other custom features in SharePoint that retrieves data from a SQL server, there are a few gotchas and pitfalls that you should be aware of. I spent a few hours battling a couple of problems, so I thought I’d document the things I found out here to spread the knowledge.
SQL access with integrated security from SharePoint - Code - eCraft Labs
Publishing reports on a daily basis to Reporting Services is trivial with the Sharepoint delivery extension and Reporting Services.
More details:
SQL Server 2005 Reporting Services Service Pack 2 (SP2) includes a delivery extension that you can use to send a report to a SharePoint library. The delivery extension is installed and configured when you apply SP2.
To use the SharePoint delivery extension, you must create a subscription from an application page on a SharePoint site, and then select SharePoint document library as the delivery type. You cannot use the SharePoint delivery extension for subscriptions that you create in SQL Server Management Studio or Report Manager.
If you’re trying to work with Windows 2008 domain controllers, things have changed slightly (read-buried). Allowing a user to allow logon locally to the controller is a bit more complex than in 2003.
Grant a Member the Right to Logon Locally
Applies To: Windows Server 2008 R2
Domain controllers, by default, restrict the types of user accounts that have the ability to log on locally. By default, only members of the Account Operators, Administrators, Backup Operators, Print Operators, and Server Operators groups have the Allowed logon locally system right. If you want to grant a user account the ability to log on locally to a domain controller, you must either make that user a member of a group that already has the Allowed logon locally system right or grant the right to that user account.
