|
|
5. “Normal” SQL Server Databases
SharePoint uses a SQL Server database to store its information. The information is stored in databases called content databases. You can have multiple content databases. However, the data is not stored in a “normalized” SQL Server database format. This is a surprise to many, as they assume the SQL database on the back–end functions like any other relational SQL database. It does not.
Because of this, it is common for organizations to want a separate, custom SQL Server database. One key reason is to scale SharePoint data. Certain lists can become quite large. By moving these lists out of SharePoint content databases into a separate custom SQL Server database you can vastly improve performance. However, once you move away from the “SharePoint SQL database” you lose the ability to display the data using the SharePoint displays.
You can also use a custom SQL Server database to start to “normalize” your information across SharePoint. Thus, you may want to have a database in SQL Server that is used as a master list. Other features throughout your SharePoint environment could access this database.
This is a major barrier because when you cross it you are in a world that is not supported by the basic UI and services components of SharePoint. However, CorasWorks through the Data Integration Toolset supports crossing this barrier quite easily. You get the same displays such as calendar and grids, forms to read and write, the data connectors, and, the ability to cross-connect this data with SharePoint data and act on it.
In Breeze, we expose the AdventureWorks database that comes with SQL Server and leverage this as part of our environment. The example below will introduce you to the standard features for breaking through this barrier.
Project Financial Data
Below is a display from the Financial tab of the Customer Project Dashboard. This is a display of expense items for projects grouped by customers. It also allows you to add, edit, and delete items. This display combines a number of data sources – it is called a mashup. The customer list is coming from SQL Server. We also use SQL Server to store the expense items. The projects are coming from SharePoint. These three sources of data are “mashed up” to create the data for the display. All of this is done with modular components without custom code development.
This display has a number of additional features that empower end-users even when working with SQL Server. As shown above the information is color coded to highlight size. In addition, the end-user can search or create filters and move columns. Further, above is shown a context sensitive menu. This is used for a number of features including displaying, creating, editing, and deleting items expense items in SQL Server. Below we show the form to edit financial information.
Click here to visit the Financial view in the Customer Project Dashboard of Breeze.
|
|