SQL Server Integration Services, using its designer interface, or BIDS, has made it possible to process data using many of the data flow related items in its Toolbox without writing a line of code. This is a very attractive option for someone who is a beginner with some knowledge of databases, and for end users who may want to look up some detail buried in the data. This tutorial by Dr. Jayaram Krishnaswamy shows how the designed package extracts data from an SQL Server 2005 and processes it using several of its built-in transformations.Read Data Processing using Derived Column and Aggregate Data Transformations in full
Once your portal is looking the way you want it to, it is time to share your creation with the rest of the world. We want to transfer our site from our local computer and set it up on the World Wide Web.
In this article by Daniel N. Egan, you will know the following:
- How to obtain a domain name for your site
- What to look for in a hosting provider
- How to modify your files to prepare for moving to a host
- How to set up your database on a hosted site
- What file permissions are needed for your site to run
Report Services, Analysis Services, and Integration Services are the three pillars of Business Intelligence in Microsoft's vision that continues to evolve. Reporting is a basic activity, albeit one of the most important activities of an organization because it provides a specialized and customized view of the data of various forms (relational, text, xml etc) that live in data stores. The report is useful in making business decisions, scheduling business campaigns, or assessing the competition. The report itself may be required in hard copy in several document formats such as DOC, HTML, PDF, etc. Many times it is also required to be retrieved in an interactive form from the data store and viewed on a suitable interface, including a web browser. The Microsoft SQL Server 2005 Reporting Services, popularly known by its acronym SSRS, provides all that is necessary to create and manage reports and deploy them on a report server with output available in several document formats. The reader will greatly benefit from reading the several articles detailed in the author's Hodentek Blog. The content for the articles were developed using VS 2003, VS 2005, SQL 2000 and SQL 2005.Read Creating a Simple Report with Visual Studio 2008 in full
This is the second part of two-part article by Vivek Thakur on N-Layer Architecture with ASP.NET 3.5. In the first part we saw the need for a 3-layered solution and examined ER-diagrams, domain models and UML. In this part we will we will explore a 1-tier 3-layer Architecture using a Domain Model and Object Data Source Controls.Read ER Diagrams, Domain Model, and N-Layer Architecture with ASP.NET 3.5 (part2) in full
In this two-part article by Vivek Thakur, we will learn about ER Diagrams, Domain Model, and N-Layer Architecture with ASP.NET 3.5. The 1-tier 1-layer architecture is the default style in ASP.NET and Visual Studio 2005/2008. To overcome the limitations of this style, we can further break the application code into n-layers, where the number "n" actually depends on the project requirements.
In this article we will:
- Learn the 2-layer style
- Understand ER diagrams
- Understand what a domain model is, and what UML relationships are
- Learn the 3-layer style
- Learn about object data source controls
In this two-part article by Chris Webb, we will cover query performance tuning, including how to design aggregations and partitions and how to write efficient MDX. The first part will cover performance-specific design features, along with the concepts of partitions and aggregations.
One of the main reasons for building Analysis Services cubes as part of a BI solution is because it should mean you get better query performance than if you were querying your relational database directly. While it's certainly the case that Analysis Services is very fast it would be naive to think that all of our queries, however complex, will return in seconds without any tuning being necessary. This article will describe the steps you'll need to go through in order to ensure your cube is as responsive as possible.Read Query Performance Tuning in Microsoft Analysis Services: Part 1 in full
In the previous part of the article by Chris Webb, we covered performance-specific design features such as partitions and aggregations. In this part, we will cover MDX calculation performance and caching. We'll see how important caching is to overall query performance.Read Query Performance Tuning in Microsoft Analysis Services: Part 2 in full
In this article by Mike Liu, we will explain the concepts and definitions related to SOA, and clarify some confusions regarding SOA. Let's discuss each of the following in detail:
- What is SOA?
- Why do we need SOA?
- What are the various approaches to implementing SOA and what are the key differences between them?
- What is a web service and how is it related to SOA?
- What standards and specifications are there for web services?
ADO.NET Data Services leverages the ADO.NET Entity Framework to build data services for relational data sources. These include support for MySQL, DB2, and Oracle in addition to MS SQL Server. It can also be used with non-relational data using an add-on provider model. With ADO.NET Data Services, the developers can build dynamic internet applications (AJAX, Silverlight, etc) that works across intranets as well as the internet. With this in place data access by applications is made possible using URI Syntax and using HTTP verbs operating on the data.
In this article by Dr. Jayaram Krishnaswamy, you will learn how to create a ADO.NET Data Service from scratch. You will also learn how you may access data using the URI constructs. The backend data for this tutorial comes from a copy of Northwind database named TestNorthwind on a named instance of SQL Server 2008. In order to work through this tutorial you should have Visual Studio 2008 SP1 installed. You also need to have .NET Framework 3.5 installed.Read Data Access with ADO.NET Data Services in full