Use the new report server configuration pages in Central Administration to grant the service accounts access to the SharePoint configuration and content databases.

Use SharePoint security to control access to report server content and operations.

Add reports and models that you created in SQL Server 2005 Reporting Services design tools to a SharePoint library. You can publish reports from Report Designer, or use the Upload action on a SharePoint library to upload any report server item. If you publish the files, be sure to specify fully qualified URLs.

An example URL for a file uploaded to Shared Documents on the top-level site of a SharePoint Web application might be :

http://example-server-name/Shared Documents/CompanySales.rdl. The URL must include a file name extension.

If the library is on a site, you must also include any sites and subsites before the library.---For more information,see "Deploying Reports, Models, and Shared Data Sources to a SharePoint Site" in SQL Server Books Online.---Create new shared data source (.rsds) files from a SharePoint site to use with the reports and models that you add to the library. A new file name extension named .rsds is introduced in this release; it is used for shared data source files that you create and store in a library.Use the new Report Viewer Web Part to view reports.

Use Report Builder from a SharePoint site. You can open or modify an existing Report Builder report definition file from a library. You can load a model in Report Builder to create new reports from report model (.smdl) files that have been uploaded or published to a SharePoint library.

Use new Web pages and configuration options to set permissions and properties on reports (.rdl), models (.smdl), resources, and shared data sources (.rsds) that you add or create on a SharePoint site. You can also use Web application pages to define schedules and subscriptions.---Note:Earlier versions of Reporting Services include two Web Parts that provide minimal integration between a report server and a SharePoint site.Those Web Parts are not part of the Reporting Services Add-in and have different requirements and functionality. ---For more informationabout how those Web Parts compare with the Web Part that is included in the Reporting Services Add-in, see "Comparing Levels of Integration Across Versions of Reporting Services and SharePoint Technologies" in SQL Server Books Online.http://www.microsoft.com/sql/default.mspx---SP2 SQL : Download Service Pack 2 for Microsoft SQL Server 2005.http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d07219b2-1e23-49c8-8f0c-63fa18f26d3a--P. Erol GIRAUDY - MVP MOSSwww.clubmoss2007.orgwww.shareclubs.org

2/16/2007

Brief Description : The Microsoft Best Practices Analyzer for Microsoft Windows SharePoint Services 3.0 and the 2007 Microsoft Office System creates detailed reports to help administrators achieve greater performance, scalability, and uptime. This tools for 2007 Office System : Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System. After the analysis is complete, open sharepointbpa.report.htm in a web browser. See also my web site on the tools for MOSS and WSSv3 : http://outilsmoss.blogspot.com/---P. Erol GIRAUDY MVP MOSSwww.clubsps.orgwww.shareclubs.org

2/13/2007

A common need is to change the theme (and the alternate style sheet) of a site when it is created. In order to do this in SharePoint 2007, you must create a feature that makes the changes and then either “staple” the feature to a site or reference the feature within the site definition.

2/08/2007

Aimless Ramblings from a Blithering Lunatic . . . : PDF Icon Update: "Ever since I blogged about my batch file to simplify the task of getting a PDF icon to display in SharePoint 2.0 document libraries back in October of 2004, it has been the single-most popular post on my blog (with almost 60,000 hits to date). Well, ever since Windows SharePoint Services 3.0 was released, I knew that I needed to update my batch file, it just wasn't quite at the top of the to-do list. But now the wait is over - I have posted an updated package here. "---P. Erol GIRAUDYwww.shareclubs.orghttp://clubmoss2007.org

2/04/2007

I was preparing for a TechReady (internal Technical Readiness conference) Presentation and for my advanced deployment presentation I really needed to beef it up. Here's a list I put together for a few lockdown slides. This is not meant to be fully comprehensive, but get you started down the right track. All of these may not apply.--P. Erol GIRAUDY MVP MOSSwww.clubmoss2007.orgwww.shareclubs.org

2/03/2007

A nice idea, I was talking to Charles Arnold after the last STC-Suncoast chapter meeting about using wikis as project documentation tools. Neil Perlin just presented on Web 2.0, and referenced James Surowiecki’s The Wisdom of Crowds: Why the Many Are Smarter Than the Few and How Collective Wisdom Shapes Business, Economies, Societies and Nations. Surowiecki’s main idea is that collective wisdom almost always outstrips individual wisdom....---I was playing around with the SharePoint 2007 wiki features and also those of Socialtext. Here are the barriers I’m up against:

Wiki wysiwig’s are primitive (technical documentation can have some complicated styles, with several levels of lists).

Once all the info is in the wiki, how do I generate a manual or online help? I don’t want to maintain two separate files.