in

SharePoint Blogs

The Best Place for SharePoint-related Blogs

heliosa's blog

  • File Shares vs. Sharepoint (RELOADED)

    Hi all,

    Many times I follow and participate of discussions on "File Servers versus Sharepoint", and in this post I would like to place my personal vision on this subject.

    Main (to begin) links on this topic:

      • Is the File Server Dead?
        An excellent resource with information on Simplified Comparison of File Server file features and SharePoint Server file features, File Server Scenarios, Disk Space and Cost Considerations and some migration techniques.

    • Joel Oleson's Blog
      • What NOT to do on SharePoint
        "The purpose of this document is to provide prescriptive guidance around the appropriate usage of Microsoft Office SharePoint 2003 as a data storage repository.

        In general terms, SharePoint is an excellent data repository upon which users can store their data, whether for personal or shared use. There are, however, specific scenarios in which SharePoint is not the optimal storage location."

      • File Shares vs. SharePoint
        Some good points on "… where file shares make more sense than SharePoint as a storage technology …"

    As a summary, this moment I think that the Sharepoint Technologies is not (and they do not have to be seen as) a competitor or replacement of the NTFS File Servers.

    I see that the Sharepoint technologies must be boarded with a new vision, focus on new models of work and its necessities of productivity improvement. People-ready business from Microsoft can help to understand some details on the changes and evolutions of our model of work.

     

    We are evolving toward a diverse yet unified global market with customers, partners, and suppliers that work together across cultures and continents. The global workforce is always on and always connected, requiring new tools to help people organize and prioritize their work and personal endeavors. Business is becoming more transparent, with a greater need to ensure accountability, security, and privacy within and across organizations.

    Software is one tool that can help your business keep pace with change. It can help you meet the challenges of this new world of work by helping you to:

    • Simplify how people work together
    • Find information and improve business insight
    • Protect and manage content
    • Reduce IT costs and improve security

    It is an investment that has the flexibility and capacity to adapt as your people increase their own capacity and output.

    Sharepoint Techs is all about productivity, collaboration, evolution of models of work knowledge management. File Servers only has in its focus the storage model, without business model-oriented focus.

    My personal conclusion:

    • Sharepoint Technologies: Business focus
    • File Servers: IT (infrastructure storage) focus

    01 - Why, Where and When to store (or to move) files for the Sharepoint-based sites (infrastructure)?

    We must think about storing files in the Sharepoint-based sites WHEN really we had intention to evolve of a simple "File Share" for a "Collaborative File Shares"; with focus in centralization, organization, security, management, personal productivity, sharing of knowledge, visibility of information, and other important points…

    Sharepoint provides some services such as:

    This differentiates the "classics File Shares" of the "Collaborative File Shares". Business Value and/or Business focus!    

    Here they are some links:



    INFORMATION ON PERFORMANCE

    One another important point in this discussions is the questioning referring the Performance (Loading will be example) in environments of collaboration based on Sharepoint.

    What it is better (or faster) for my users? Open one file stored in the "File Share" or in the "Sharepoint-based site"???

    As we know, the storage-architecture of data in Sharepoint Technologies is based on the MS SQL Server; using the fields BLOB to provide storage of great amounts of information. (limit of 2Gb of data)

    Some weeks ago I read an interesting article on the storage of files in the SQL Server (Databases) or in File Shares; with focus in the performance of the access (user). You can have access this article in the site of the Microsoft Research – article To BLOB or Not To BLOB: Large Object Storage in a Database or a Filesystem?
    The conclusion of this article is "if objects are larger than one megabyte on average, NTFS has a clear advantage over SQL Server. If the objects are under 256 kilobytes, the database has a clear advantage."

    I think that these conclusions are sufficiently interesting, but also see that the MS Office (Desktop programs and Servers) Teams had made an excellent work with regard to architecture of the products, raising the performance of the products with this characteristic (Database Storage).

    I believe that an excellent planning of architecture (infrastructure) at enterprise environment can raise performance levels (Sizing, capacity planning and more…). Here goes some important links:

    Chapter overview: Plan for performance and capacity (Office SharePoint Server)

    The articles in this chapter include:

    Hey guys, What do you think about this?

     

    Obs.: Another great discussion is with regard to the use of the Sharepoint Technologies as an evolution (replacement) of the MS Exchange Server Public Folders. As this topic also is extensive, they follow some links interesting: (I´ll write details in one another chance)

     

  • Tips & Tricks in Using Wikis and Blogs

  • You know the Office Groove 2007???

    Hi all,

    Some weeks behind I participated of one round-table in the Microsoft Brazil related to Office Groove 2007! You know the Office Groove 2007???

    I sincerely did not have full knowledge of this new tool, through fast readings I already understood its focus - Sharing of information between teams with rapidity, agility and ……. you know, all about Collaboration!
    But I always thought: "OK, and Sharepoint Products and Technologies 2007? Microsoft launched two tools for the same necessity?? (I do not believe ... crazy ideia!!! heheheh)

    Ok, I just participated of the training to know this such of Groove … in which way it is related (or not) with the Sharepoint Techs!!! 
    Wink

    Abbott Lowell, Senior Technical Product Manager (Office Groove team > Microsoft Office Enterprise group) was our intrutor.

    Some subjects of the training:

    What is Office Groove?

    "Office Groove 2007 is a collaboration software program that teams can use to share information and work together on project activities — from simple document collaboration to custom solutions integrated with business processes. Teams using Office Groove 2007 work inside collaborative workspaces, which put all team members, tools, and information in one place. Groove workspaces keep teams up to date automatically and efficiently, and enable them to work anywhere, anytime, and with anyone, so they spend less time coordinating and more time working." from Office Online


    It´s important to know that the Groove 2007 is part of the Office Enterprise 2007.


    Learn more on 2007 Microsoft Office system suites

    Some interesting points (highlights above):

    1. Software Program > YES, Groove 2007 is one desktop (installed) program. Technical similar "windows forms" applications (EXE files).
      [Sharepoint Techs 2007] – Is Web-based collaboration technology!

    2. Collaboration anywhere and anytime > Because Groove stores workspaces and the data they contain right on your computer, not on a central server. You can access and update the information in your workspaces whether you are connected to the network or not. Each time you make a change—for example, update a file, respond to a discussion, or post some text in the workspace chat area—Groove sends your change (and only the change) automatically to all the members of your workspace.

      If you are not online when you make the change, Groove sends it when you next connect. If your team members are not connected, then they get the change the next time they connect.

      !!! Peer-to-Peer Collaboration !!!

      [Sharepoint Techs 2007] – The web-based architecture of the Sharepoint Techs limits its use in a centered (central server based) and online environment.
      [Obs.: Ok Sharepointers, We can use Office Outlook 2007 to access some document libraries in offline mode. But the synchronization capabilities not yet are enough.] L

    3. Collaboration with anyone > You can create a Groove workspace in minutes, add the right tools for the job, and invite anyone to join — employees, customers, or partners — with advanced security and without worrying about server space.

      [Sharepoint Techs 2007] – The distribution of information from the Sharepoint-based web sites is not enough flexible. The centered security model based on Active Directory (or in any other provider) is one another point. Mainly when we need to work with employees, customers, or partners in a SHARED (and) EXTERNAL collaboration environment.

    For these reasons I believe that the Groove 2007 and the Sharepoint Techs 2007 can be complementary in a corporate collaboration environment. J

    Groove 2007 to Dynamic Teamwork, and Sharepoint Techs 2007 to Broad Information Sharing and Workflow.

    In next posts I will say more on the capabilities of deployment, customization, sharepoint and client-side integration, etc…
     
    Here goes some links of the Groove docs:
    I think that the Groove 2007 is really a good idea, and at this moment a nice product (good architecture and technological innovation). But I also think that many points still can (and they need) be improved - like integration with Office client (Outlook and OneNote mainly), Office Server (adds Sharepoint features and Forms Server), Exchange Server and etc...
     
    Stay tuned!!!

    []´s

    Hélio Sá Moreira
    MOSS MVP

  • Microsoft Brasil - Innovation Day - ISV Partners

    Olá pessoal,

    Ontem tive o prazer de participar como palestrante de um ótimo evento realizado na Microsoft Brasil, como foco em ISV Partners, chamado Innovation Day. Este evento é cíclico, ocorre mensalmente (se não me engano) e tem como intuito repassar aos parceiros visões detalhadas de novas tecnologias, novas oportunidades de negócio e, é claro, novas e revolucionárias formas de desenvolvermos sistemas/soluções.

    Esse mês foi a vez do Sharepoint, sendo abordado neste Innovation Day com foco nas possibilidades de utilização como uma real (robusta, escalavel, extensível, performática e produtiva) plataforma de desenvolvimento e distribuição de soluções corporativas.

    Um assunto incrívelmente interessante (Ok, sei que sou suspeito para falar! :-)), mas também incrivelmente extenso para ser abordado em uma tarde somente.

    A Aline Rokutan (MS Brasil), minha amiga pessoal de muito tempo, foi a responsável pelo material e também pela agenda. Alias, ficam aqui os meus parabéns pela escolha dos seguintes temas:

    • Colaboração
    • Portais
    • Gestão de Conteúdo

    As demos e todo o conteúdo proporcionado tinham como intuito demonstrar todo o poder do Sharepoint como plataforma-base para o desenvolvimento de soluções corporativas - com uma primeira abordagem teórica e conceitual, seguido de um grande deep-dive sob algumas das principais funcionalidades.

    Ah, fica aqui registrado o meu agradecimento à Aline, pois foi ela que me convidou para participar deste grande bate-papo. ;-)

    Participei dos Q&A´s que surgiram, e fiz uma apresentação/demo focada em Sharepoint 2007 Event Handlers!!! (Mto bacana...)

    Para quem participou, vejam o arquivo EventHandlers.zip anexado à este post. Enjoy it!!! (Por questões de tamanho, retirei do package as referências ao Microsoft.Sharepoint.dll)

    Espero que os participantes tenham gostado, e já estejam pensando bastante em como utilizar o Sharepoint 2007 da melhor forma possível em seus ambientes.

    Fiquem com este blog como meu ponto principal de contato, espero poder compartilhar cada vez mais informação com todos.

    Abraços

    Hélio Sá Moreira
    MOSS MVP

  • NEWS: Microsoft Interactive Media Manager

    Hi all,

    Microsoft announced one new "geek toy" for us – the Microsoft Interactive Media Manager "is a next-generation digital content management solution that combines digital workflows and media application integration with a collaborative front-end environment".

    For "sharepointers", is important to say that Microsoft Interactive Media Manager is one extension of MOSS (Office Sharepoint Server 2007) platform, and is designed specifically for the media and entertainment industry, including film and post-production studios, broadcasters, game developers, publishers, and advertising and marketing agencies.

    Technically, I think that Microsoft Interactive Media Manager will work as one new solution package for MOSS. (Nice job!!!)

    I would like to test this ASAP. J

    Sharepoint Player Control of Microsoft Interactive Media Manager

    Here are some Sharepoint objects that composes this solution.
    • Media Library serves as a front end in which media content items in the digital asset management system are displayed as thumbnails.
    • Media Viewer displays information such as annotations and time codes in Society of Motion Picture and Television Engineers format and offers sophisticated, built-in playback controls. 
    • Media Annotator allows groups of people to collaborate on media assets through video annotations, digital inking and discussions.
    • Media Import facilitates the upload of media files and automatically launches associated workflows, such as information-gathering processes.
    • Media Cart provides an individualized area for storing media assets that people want to edit themselves or push out to appropriate editors.

    []´s

    Hélio Sá Moreira
    MOSS MVP

  • Microsoft MVP Award Renewed!

    Hi guys,

    Today my MVP Award for Office Sharepoint Server was renewed!!! I got a mail from Microsoft on April 1st ....

    Again, I'm very honored! Thanks Microsoft!!!

    []´s 

    Hélio Sá Moreira
    MVP - Sharepoint Portal Server

  • SQL Server 2005 Service Broker :: Understanding and Implementing (DEMO SCRIPT)

    Hi all,

    The SQL Server 2005 is a platform composed by many interesting services. The Service Broker is one of these new services, with focus on queuing and reliable messaging for SQL Server - Ass

    As new technology based on SQL Server 2005 Database Engine, Service Broker provides a robust asynchronous programming model. "Database applications typically use asynchronous programming to shorten interactive response time and increase overall application throughput."

    Imagine all the basic requirements of an asynchronous process implemented at engine level of the SQL Server 2005 - using its main characteristics like security, scalability, productivity, performance and robust plataform of services for LOB apps. -> It´s SQL Server 2005 Service Broker! :-)

    I recommend following links for more details:

    After to understand the Typical Uses of Service Broker, it´s necessary to make familiar to the object model of the Service Broker - based on T-SQL. See Introduction to Service Broker Programming page from Service Broker Developer InfoCenter.

    Follows below one commented step-by-step script to test and understand the basic functioning of the Service Broker. (my personal SSSB demo!) Yes 

    /***************************************************************************************************
     * SQL SERVER 2005 Service Broker Test script by Hélio Sá Moreira                        */

    --Create test DB to Service Broker demo
    CREATE DATABASE DB_SERVICEBROKERTESTER;

    --Activate Service Broker feature on test DB
    ALTER DATABASE DB_SERVICEBROKERTESTER
       
    SET ENABLE_BROKER;

    /*NOTE: Explicit enable SSSB on Test DB. For more details see How to: Activate Service Broker Message Delivery in Databases (Transact-SQL)*/

    GO

    USE DB_SERVICEBROKERTESTER

    --Check if Service Broker is activated on test DB
    SELECT db_name(),
                  is_broker_enabled
      
    FROM sys.databases
    WHERE database_id = db_id()

    --Create symmetric database master key (REQUIRED)
    CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'Hey_Guys_P@ss'

    /*NOTE: The database master key is a symmetric key used to protect the private keys of certificates and asymmetric keys that are present in the database. When it is created, the master key is encrypted by using the Triple DES algorithm and a user-supplied password. To enable the automatic decryption of the master key, a copy of the key is encrypted by using the service master key and stored in both the database and in master.*/
    /*REFERENCE: CREATE MASTER KEY (Transact-SQL) and How to: Create a Database Master Key*/

    /********************************** SERVICE BROKER OBJECTS **********************************/

    CREATE MESSAGE TYPE SBTest_RequestMessage
    VALIDATION
    = WELL_FORMED_XML

    CREATE MESSAGE TYPE SBTest_ResponseMessage
    VALIDATION
    = WELL_FORMED_XML

    /*NOTE: A message type defines the name of a message and the validation that Service Broker performs on messages with that name. Both sides of a conversation must define the same message types.*/
    /*REFERENCE:
    CREATE MESSAGE TYPE (Transact-SQL)*/


    CREATE CONTRACT SBTest_Contract
    (
      
    SBTest_RequestMessage SENT BY INITIATOR,
       SBTest_ResponseMessage SENT
    BY TARGET 
    )

    /*NOTE: A contract defines the message types used in a Service Broker conversation and also determines which side of the conversation can send messages of that type. Each conversation follows a contract. The initiating service specifies the contract for the conversation when the conversation begins. The target service specifies the contracts that the target service accepts conversations for.*/
    /*REFERENCE:
    CREATE CONTRACT (Transact-SQL)*/


    CREATE QUEUE RequestBOX

    CREATE QUEUE ResponseBOX

    /*NOTE: Queues store messages. When a message arrives for a service, Service Broker places the message on the queue associated with the service.*/
    /*REFERENCE:
    CREATE QUEUE (Transact-SQL)*/


    CREATE SERVICE SBTest_RequestService
    ON QUEUE RequestBOX
    (
      
    SBTest_Contract
    )

    CREATE SERVICE SBTest_ResponseService
    ON QUEUE ResponseBOX
    (
       SBTest_Contract
    )

    /*NOTE: A Service Broker service is a name for a specific task or set of tasks. Service Broker uses the name of the service to route messages, deliver messages to the correct queue within a database, and enforce the contract for a conversation.*/
    /*REFERENCE:
    CREATE SERVICE (Transact-SQL)*/

    /******************** HOW TO SEND A MESSAGE - REMEMBER: ASYNCHRONOUS MODE ********************/

    DECLARE @DialogDHL             UNIQUEIDENTIFIER,
                   
    @MessageContent    XML

    SET @MessageContent = '<SBTest>' +
                                          
    '   <Message LCID="1046">' +
                                          
    '      Hey, my first async message....' + 
                                          
    '   </Message>' + 
                                          
    '</SBTest>'

    BEGIN DIALOG CONVERSATION @DialogDHL
     FROM SERVICE SBTest_RequestService
          
    TO SERVICE 'SBTest_RequestService'
        
    ON CONTRACT SBTest_Contract

    /*NOTE: Begins a dialog from one service to another service. A dialog is a conversation that provides exactly-once-in-order messaging between two services.*/
    /*REFERENCE: BEGIN DIALOG CONVERSATION (Transact-SQL) */ 

    ;SEND ON CONVERSATION @DialogDHL
    MESSAGE TYPE SBTest_RequestMessage (@MessageContent) ;

    /*NOTE: Sends a message, using an existing conversation.*/
    /*REFERENCE: SEND (Transact-SQL) */

    /*******************************************************************************************************************************/

    /*************************************** CHECK IF MESSAGE EXISTS IN QUEUE *************************************/

    --Simple SELECT statement on QUEUE
    SELECT * FROM dbo.RequestBOX

    --(Result set ...)

    /*******************************************************************************************************************************/

    /******************************************* HOW TO RECEIVE A MESSAGE *******************************************/

    DECLARE @DialogDHL UNIQUEIDENTIFIER,
                   
    @MessageType NVARCHAR(256),
                   
    @MessageContent XML

    ;RECEIVE TOP(1) @DialogDHL = conversation_handle,
                              
    @MessageType = message_type_name,
                               @MessageContent
    = message_body 
          
    FROM RequestBOX

    /*NOTE: Retrieves one or more messages from a queue. Depending on the retention setting for the queue, either removes the message from the queue or updates the status of the message in the queue.*/
    /*REFERENCE: RECEIVE (Transact-SQL) */ 

    SELECT @MessageType, @MessageContent

    END CONVERSATION @DialogDHL

    /*NOTE: Ends one side of an existing conversation.*/
    /*REFERENCE: END CONVERSATION (Transact-SQL)  */ 

    /*******************************************************************************************************************************/

    I think that to start and to understand the Service Broker and its basic functioning, this stey-by-step is sufficiently interesting. :-)
     
    In next posts I will approach new concepts (more advanced) as Queue Activation, receive messagens using WAITFOR T-SQL statement, GET CONVERSATION T-SQL statement and some troubleshooting scripts.
     
    []´s
  • Enterprise Search Architecture in SharePoint Technologies 2007

    Hi all,

    In my last post I wrote about differences of the search services in the Sharepoint Technologies 2007 - Search in SharePoint Technologies 2007.

    The architecture of search service is composed for many components (shows on Figure 1), and its important to say that Enterprise Search uses the same underlying Search service as Search in Microsoft Windows SharePoint Services. (great news).

     

    Following are the components of the Search service's architecture. (from Enterprise Search Architecture)

    • Index Engine: Processes the chunks of text and properties filtered from content sources, storing them in the content index and property store.

    • Query Engine: Executes keyword and SQL syntax queries against the content index and search configuration data.

    • Protocol Handlers: Opens content sources in their native protocols and exposes documents and other items to be filtered.

    • IFilters: Opens documents and other content source items in their native formats and filters into chunks of text and properties.

    • Content Index: Stores information about words and their location in a content item.

    • Property Store: Stores a table of properties and associated values.

    • Search Configuration Data: Stores information used by the Search service, including crawl configuration, property schema, scopes, and so on.

    • Wordbreakers: Used by the query and index engines to break compound words and phrases into individual words or tokens.

    Developers can use these components through Search SQL Syntax (WSS) or Enterprise Search SQL Syntax (MOSS), APIs (Object Model - WSS and/or MOSS) or XML Web Services provided by WSS and MOSS.

    To get more detail´s on Enterprise Search Architecture in SharePoint Technologies 2007, see Enterprise Search Architecture from Microsoft.

    []´s

  • Search in SharePoint Technologies 2007

    Hi all,

    Today I had a meeting with some colleagues on the characteristics, new features and enhancements of the search service in Sharepoint 2007. I´m writing this post to share some informations ....

    First, it´s important to say that Search capabilities are very different based in the product that we use. Products can be:

    • Windows SharePoint Services 3.0
      Windows SharePoint Services is a versatile technology included in Microsoft Windows Server™ 2003 that enables organizations and business units of all sizes to increase the efficiency of business processes and improve team productivity.

    • Office SharePoint Server 2007 for Search 
      The ability to search for information in enterprise Web sites is critical to the effective use and usability of those sites. Search in Office SharePoint Server 2007 is a shared service that provides extensive and extensible content gathering, indexing, and querying. This service supports full-text searching by using Structured Query Language (SQL)–based query syntax, and it provides new keyword syntax to support keyword searches. Search is covered in more detail elsewhere in this document, in the section titled Enterprise Search.

    • Enterprise Search in Microsoft Office SharePoint Server 2007
      Office SharePoint Server 2007 is an integrated suite of server capabilities that can help improve organizational effectiveness by providing comprehensive content management and Enterprise Search, accelerating shared business processes, and facilitating information sharing across boundaries for better business insight. Office SharePoint Server 2007 supports all intranet, extranet, and Web applications across an enterprise within one integrated platform, instead of relying on separate fragmented systems. Additionally, this collaboration and content management server provides IT professionals and developers with the platform and tools they need for server administration, application extensibility, and interoperability.


    Search in Microsoft Windows SharePoint Services, Office SharePoint Server 2007 for Search,and Enterprise Search in Microsoft Office SharePoint Server 2007 are all based on the same Microsoft Search core indexing engine, ensuring consistent search across Office SharePoint Server 2007 and Windows SharePoint Services 3.0.

    However, there are differences among the SharePoint search versions. The following table provides a comparison of features among Search in Microsoft Windows SharePoint Services, Office SharePoint Server 2007 for Search, and Enterprise Search in Microsoft Office SharePoint Server 2007.  

    Comparing Search Versions document from SharePoint Server 2007 SDK on MSDN. These three products have differences of implementation with relation to the following characteristics:

    • What can be indexed
    • Rich, relevant results
    • Alerts, RSS, Did you mean? and Collapsing of duplicates
    • Best bets and Results removal, Query reports
    • Search Center / Tabs
    • People search and Knowledge network
    • Business Data Search
    • Query Web service
    • Security trimming of search results
    • Query syntax
    • APIs

    See Comparing Search Versions document! :-)

    Entry-Level search solutions typically take Internet search technologies and apply them to the enterprise environment.  They offer a basic feature set at a low cost.

    Specialized search solutions are at the other end of the spectrum.  Solutions in this category are feature rich and offer a wide variety of functionality for both the end user and the administrator. But the additional features can come with a hefty price tag.

    Enterprise Search from Microsoft is changing competitive landscape in two important ways.

    First, our solution offers a unique combination of functionality at a very competitive price point, creating a new category in the market—a category that we think represents true Enterprise Search.


     
    Second, our integration with the Windows desktop and Microsoft Office SharePoint Server means that Enterprise Search from Microsoft is an integral part of a broader business productivity infrastructure.  In essence, we’ve added a whole new dimension to the Search discussion.

    This has three benefits:

    • Out-of-the-box integration: Search as an integral part of a business productivity platform means that search is integrated with your collaboration, portal, content management, and business process platform—right out-of-the-box.
       
    • Rich, actionable interfaces: Search as an integral part of a business productivity platform not only helps people find what they need, but also helps them do something meaningful with what they’ve found.  Rich, actionable interfaces in Office SharePoint Server, Windows, and business productivity applications like Microsoft Outlook make it easy to turn search results into action.
    • Reduced IT costs: Search as an integral part of a business productivity platform helps IT professionals consolidate their investments and reduce the costs associated with buying, implementing, and maintaining individual applications.

    []´s

  • Next week >> 2007 MVP Global Summit in Microsoft/USA

    Hi all,

    In the next week we have a great event  - MVP Global Summit - in Microsoft USA :: Redmond - Seattle, WA.

    2007 MVP Global Summit is a BIG meeting between MVP's and Product Teams at Microsoft. We can participate of deep dive session related to many areas of interest. (Sharepoint .... hehehehe)

    It´s a great pleasure to be able to talk with the biggest specialists of the world, including some professionals who I frequent follow through its blogs.

    From Microsoft:

    MVPs like Jan Tielens, Dustin Miller, Patrick Tisseghem and others ...

    If I will be able (because the majority of the content is protected by an extensive NDA), I will share some experiences.

    OHHH, I cannot forget the Bill Gates keynote!!! ;-)

    []´s

  • SharePoint Designer 2007: Product Info, Online Demos and Team blog ...

    Hi all,

    I would like to share some information on Sharepoint Designer 2007, an essential tool for professionals who work with sharepoint - like Information Workers, Designers and Developers. First is necessary to understand the evolution (The future of FrontPage) and the new positioning of Sharepoint Designer 2007.

    Some important links:

    I found some demonstrations of the Sharepoint Designer in the Office online.

    Demos: A six-part series on getting the most out of SharePoint Designer 2007

    1. Powerful user interface and design tools
    2. Customize SharePoint sites
    3. Create and modify layout pages
    4. Create and modify rules-based workflow applications
    5. Build composite no-code SharePoint applications
      Visual Studio integration

    Microsoft SharePoint Designer Team Blog is a great source of information too.

    Good work ...

    []´s

     

  • Get Started Tab (Add-in) for Office System 2007

    Hi all,

    Today I installed some add-ins for the Office System 2007 - more specifically the Excel 2007, Word 2007 and PowerPoint 2007 - the Get Started Tab Add-in.

    These add-ins add new tab in the ribbon. On this tab give you easy access to free content on Office Online that helps you learn Word | Excel | PowerPoint 2007 quickly.

    See Get Started Tabs ...

    Download from MS Download:

    []´s

  • MS SQL Server 2005 Data Mining Add-ins for Microsoft Office 2007

    Hi all,

    With Service Pack 2 of SQL Server 2005, the Data Mining Add-ins for Microsoft Office 2007 was RTW (Release To Web), adding some interesting Data Mining functionalities to the Excel 2007 and/or Visio 2007.

    Microsoft SQL Server 2005 Data Mining Add-ins for Microsoft Office 2007 (Data Mining Add-ins) allow you take advantage of SQL Server 2005 predictive analytics in Office Excel 2007 and Office Visio 2007. The download includes the following components:

    • Table Analysis Tools for Excel: This add-in provides you with easy-to-use tasks that leverage SQL Server 2005 Data Mining under the covers to perform powerful analytics on your spreadsheet data.
    • Data Mining Client for Excel: This add-in allows you to go through the full data mining model development lifecycle within Excel 2007 using either your spreadsheet data or external data accessible through your SQL Server 2005 Analysis Services instance.
    • Data Mining Templates for Visio: This add-in allows you to render and share your mining models as annotatable Visio 2007 drawings.

    Each of the above components may be separately installed.

    Data Mining add-ins works with Professional, Professional Plus, Ultimate and Enterprise editions of 2007 Office System.

    Excel 2007 -- Data Mining ribbon and Table Tools conext:


    Excel 2007 Charts based on DM capabilities.

    In Visio 2007, DM add-in works with new PivotDiagram feature:



    For details, follow some interesting links.

    []´s

  • EMC Documentum: a competitor for Sharepoint Techs?

    Hi all,

    Many people ask to me which the main competitors for Sharepoint. Before answering, I list the main characteristics of the Sharepoint Technologies 2007.

    Basically 6 SharePoint Investment Areas, over one Plataform Services (aka WSS).

    It´s important to remember that Sharepoint Technologies 2007 is part of a complete and extensive Business Productivity Infrastructure platform (Streamline the way people do business with 2007 Office system).

    Ok, these 2 figures above demonstrate the complete architecture of the Sharepoint Technologies 2007.

    Back to competitors ..... today I´m reading some information on a solution of EMC2, called Documentum.

    "The EMC Documentum family helps you manage all types of content across multiple departments within a single repository. With a unified repository, various groups can easily share and reuse their content with other areas of the business that would benefit from access to this valuable information. Our product family also allows your business to share its content safely with outside organizations, including partners, vendors, and customers." from Documentum Family

    Documentum Family is composed for a series of products, with focus on:

    • Core Platform
    • Business Process Management
    • Content Collaboration
    • Compliance
    • Content Management for SAP
    • Digital Asset Management
    • Document Management
    • Enterprise Content Integration
    • Information Rights Management
    • Records Management
    • Report Management
    • Web Content Management

    (sufficiently similar to our Sharepoint? they agree?)  :-)

    This platform of the EMC2 is composed for a series of different - but integrated - products. It follows the list of products . . .

    Products of Documentum Family

    Core Platform

    All Documentum applications are based on a common, unified platform that provides a wealth of repository, content, and process services available for all content types.

    Business Process Management

    Defines, executes, monitors and optimizes business processes consistently and reliably across organizations, systems, and applications. The Documentum Process Suite facilitates automation of both high-volume transactional processes and complex collaborative processes.

    Content Collaboration

    Brings together people, processes, and content across an organization. Project teams can easily capture content and contextual information as part of their content management applications, bringing it into a corporate repository where it can be managed with other business information.

    Compliance

    Ensures that your enterprise content is complete, accurate, and protected from inappropriate use or disclosure. Your content is always readily accessible to regulators, auditors, and employees when needed.

    Content Management for SAP

    Provides a single platform, which consists of a set of SAP archiving and content management services that can be deployed incrementally in order to satisfy evolving customer SAP requirements.

    Digital Asset Management

    Manages in a unified repository all your product images, streaming video, audio files, logos, flash animations, presentations, and Web pages.

    Document Management

    Delivers a platform for enterprise document management that addresses every stage of the document lifecycle – from creation through reviews, approval, delivery, to archiving and disposal.

    Enterprise Content Integration

    Extends access to content within and outside the enterprise, making searches faster and more intelligent, and enabling end users to more logically and easily organize the content they're interested in.

    Information Rights Management

    Helps companies and government agencies actively, control, secure, and track sensitive information outside the repository.

    Records Management

    Ensures that documents of all types and from all sources are captured and maintained by a common system or toolset in accordance with both internal and external mandates.

    Report Management

    Delivers a cost-efficient transformation of print streams into documents and data that can be rapidly accessed to drive greater efficiency and improve responsiveness to customer requests.

    Web Content Management

    Efficiently manages content and underlying processes for your Web properties, and ensures that they are responsive to business needs. You'll tame Web sprawl, power portals, increase productivity, and deliver a superior user experience.

    []´s


Need SharePoint Training? Attend a SharePoint Bootcamp!

Posts (c) their respective authors. Everything else (c) 2007 SharePoint Experts