• Sign In
 
  • MSDN Blogs
  • Microsoft Blog Images
  • More ...
Search
  • Advanced search options...
Tags
  • .NET
  • Altova
  • blogging
  • code samples
  • Codeplex
  • Custom XML
  • DII
  • DIS29500
  • ECMA-376
  • IBM
  • Java
  • Monarch
  • ODF
  • Office 2007
  • OpenXMLDeveloper.org
  • PHP
  • Redmond
  • SharePoint
  • System.IO.Packaging
  • TechEd
  • UOF
  • VSTO
  • Windows
  • WordprocessingML
  • workshops
Archives
Archives
  • January 2012 (1)
  • October 2011 (1)
  • July 2011 (2)
  • April 2011 (1)
  • March 2011 (3)
  • December 2010 (1)
  • August 2010 (1)
  • June 2010 (1)
  • May 2010 (1)
  • April 2010 (3)
  • March 2010 (1)
  • November 2009 (4)
  • October 2009 (1)
  • September 2009 (2)
  • July 2009 (2)
  • June 2009 (4)
  • May 2009 (5)
  • April 2009 (4)
  • March 2009 (4)
  • February 2009 (2)
  • January 2009 (4)
  • December 2008 (4)
  • November 2008 (3)
  • October 2008 (4)
  • September 2008 (3)
  • August 2008 (2)
  • July 2008 (5)
  • June 2008 (7)
  • May 2008 (5)
  • April 2008 (8)
  • March 2008 (14)
  • February 2008 (15)
  • January 2008 (13)
  • December 2007 (12)
  • November 2007 (5)
  • October 2007 (9)
  • September 2007 (6)
  • August 2007 (10)
  • July 2007 (9)
  • June 2007 (8)
  • May 2007 (12)
  • April 2007 (14)
  • March 2007 (12)
  • February 2007 (10)
  • January 2007 (17)
  • December 2006 (14)
  • November 2006 (10)
  • October 2006 (11)
  • September 2006 (12)
  • August 2006 (12)
  • July 2006 (12)
  • June 2006 (23)
  • May 2006 (14)
Common Tasks
  • Blog Home
  • Email Blog Author
  • About
  • RSS for comments
  • RSS for posts

Business Data Catalog Simplified

Doug Mahugh - Office Interoperability
MSDN Blogs > Doug Mahugh > Business Data Catalog Simplified

Business Data Catalog Simplified

Doug Mahugh
17 Jul 2006 10:55 AM
  • Comments 2

If you've ever seen a demo of the cool new BDC functionality in Microsoft Office Sharepoint Server 2007, you've probably come away with two conclusions:

1) It's an incredibly powerful and flexible concept. (XML configuration files that connect Sharepoint's search functionality to back-end databases, web services, and other types of custom applications.)

2) It looks like a pain in the ass to work with. The required XML files are very complicated, and -- as several of my friends in the TAP and Ascend programs have politely pointed out -- Microsoft doesn't provide a high-level tool for creating and managing BDC connectors. Creating the required XML in Notepad (or even VS) can be daunting.

Well, item #2 just went away. Todd Baginski has rolled up his sleeves and built a slick comprehensive tool for working with BDC connectors, which lets you create a typical connector by simply clicking on various settings in the UI he has built. His program generates the required XML metadata automatically for you, no manual setup required.

You can read all about it here, including sample screen shots: http://www.sharepointblogs.com/tbaginski/archive/2006/07/16/9259.aspx

Or if you can't wait to try it, go straight here for the download: http://www.sharepointblogs.com/files/97/tbaginski/entry9258.aspx

Note that it doesn't support SQL 2000 yet (only SQL 2005 for now), but Todd says he'll add that in the next few days. After stepping up and being the first to deliver a tool like this, I think we can take him at his word on that. Nice work, Todd!

  • 2 Comments
SharePoint, BDC
Comments
  • Business Data Catalog Simplified » Wagalulu - Microsoft » » Business Data Catalog Simplified
    17 Jul 2006 11:15 AM
    PingBack from http://microsoft.wagalulu.com/2006/07/17/business-data-catalog-simplified/
  • Ryan Rogers [MSFT]
    20 Jul 2006 6:41 PM
    While Todd is the first to deliver a tool with a UI that I know of, one of the BDC PMs helped get a command-line metadata generator up on CodePlex here back in May:

    Database Metadata Generator for the Business Data Catalog
    http://www.codeplex.com/Wiki/View.aspx?ProjectName=DBMetadataGenerator
Page 1 of 1 (2 items)
  • © 2012 Microsoft Corporation.
  • Terms of Use
  • Trademarks
  • Privacy Statement
  • Report Abuse
  • 5.6.402.223